Managing Service User Discovery and Service Launch Object Placement on a Device

ABSTRACT

Methods and apparatuses to manage service user discovery and service launch object placement on a device. A method comprising: obtaining information to assist in identifying a portion of a user interface of a wireless device, the wireless device communicatively coupled to a network system over a wireless access network; determining a differentiating attribute of the identified portion of the user interface; obtaining one or more service launch objects for placement in the identified portion of the user interface; and sending configuration information to the wireless device over the wireless access network to assist the wireless device in placing the one or more service launch objects in the identified portion of the user interface.

BACKGROUND

As the computing power of mobile devices (e.g., smart phones, tablets,etc.) has increased, mobile devices have become capable of sending andreceiving increasing amounts of data. In addition to e-mail and textmessages, many of today's mobile devices can support a variety ofapplications that send large quantities of information to and from endusers. For example, in addition to sending e-mail and text messages,many of today's mobile devices can deliver news, weather, sports, maps,social networking information, music, videos, high-resolutionphotographs, documents, presentations, and other kinds of information.Furthermore, users can take advantage of applications that providetransactional services, e.g., shopping for content (books, music,videos, etc.) or applications.

The increased computing power of mobile devices has led to an explosionin the number of applications that are available for mobile devices.Hundreds of thousands of applications are available for Android-baseddevices and for Apple-based devices, and the number of availableapplications continues to grow at a rapid pace. Many of theseapplications are available for subscribers to download or purchasethrough an electronic “app store” or “marketplace.” A subscriber mayfind applications of interest to him or her by typing in a search wordor phrase in a field in a search field offered by the app store ormarketplace, or he or she may find an application by browsing a listoffered by the app store or marketplace (e.g., popular applications).Often, however, subscriber visits to the app store are “hit and miss”unless a subscriber happens to know the name of a desired application orhappens to type in a search word or phrase that results in theapplication being presented.

For application developers, encouraging subscribers to see, download,purchase, or use their applications can be important to the applicationdevelopers' success because their revenues often depend on purchases,downloads, and/or use of their applications. Yet because of the sheernumber of applications available through marketplaces and app stores,and because of how subscribers may behave when browsing through themarketplace or app store, application developers have little controlover whether a subscriber even finds their applications.

SUMMARY

Disclosed herein are methods and apparatuses for managing service userdiscovery and service launch object placement on a mobile device.Disclosed is a method comprising obtaining information to assist inidentifying a portion of a user interface of a wireless device, thewireless device communicatively coupled to the network system over awireless access network, determining a differentiating attribute of theidentified portion of the user interface, obtaining one or more servicelaunch objects for placement in the identified portion of the userinterface, and sending configuration information to the wireless deviceover the wireless access network, the configuration information at leastconfigured to assist the wireless device in placing the one or moreservice launch objects in the identified portion of the user interface.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a user interface (UI) Location Management System inaccordance with some embodiments.

FIG. 2 shows a two-partition UI service launch partition shown on asecondary device screen in accordance with some embodiments.

FIG. 3 shows a service launch objects shown on a device main screen inaccordance with some embodiments.

FIG. 4 shows an expanded view of a free data services single partitionUI service launch partition shown in FIG. 2 in accordance with someembodiments.

FIG. 5 shows an expanded view of paid data services single partition UIservice launch partition shown in FIG. 2 in accordance with someembodiments.

FIG. 6A shows a service launch object shown in permanent launch UI areain accordance with some embodiments.

FIG. 6B shows a service launch object icon appearance modification (inthis example case to indicate paid access vs. sponsored access services)in accordance with some embodiments.

FIG. 7 shows a service launch object shown in an application stable inaccordance with some embodiments.

FIG. 8 shows various proximity messages in accordance with someembodiments.

FIG. 9 shows a two-partition UI service launch partition with a serviceobject notification message in accordance with some embodiments.

FIG. 10 shows a service and application marketing messages on servicelaunch object icons located in a main device screen and a permanentlaunch bar in accordance with some embodiments.

FIG. 11 shows a service and application marketing messages on servicelaunch object icons located in an application stable in accordance withsome embodiments.

FIG. 12 shows a usage indication and purchase feature on service launchobjects in accordance with some embodiments.

FIG. 13 shows a three-partition UI service launch partition thatincludes sponsored or free services, paid services, and trial offerservices in accordance with some embodiments.

FIG. 14 shows a service launch object notification message with servicelaunch object specific warning on service cost in present network state(in this case a roaming usage warning for a high data usage applicationand a highlight UI icon to emphasize roaming state) according toembodiments.

FIG. 15 shows a service launch object secondary notification messagedisplayed after user chooses to launch the service or application (inthis case a secondary roaming usage warning for a high data usageservice or application) according to embodiments.

FIG. 16 shows a service launch object notification message with accessservice pricing according to embodiments.

FIG. 17 shows a service launch object notification messages showing goodquality-of-service (QoS) for a voice service and marginal QoS for avideo service according to embodiments.

FIG. 18 shows a service launch object notification message with specialpricing offer message (in this example a time of day based specialpricing message) according to embodiments.

FIG. 19 shows a service launch object notification message withgeography and time based limited offer message (in this case 50% offYouTube in the current geographic area for the next two hours) accordingto embodiments.

FIG. 20 shows a service launch object notification message with specialoffer to trade service usage points for discounted access services (inthis case free Skype in exchange for usage points on browser searchwhere search provider generates ad revenue when user uses the service)according to embodiments.

FIG. 21 shows a UI location management console UI template for a networkmanager to define a policy event notification to notify users inaccordance with some embodiments.

FIG. 22 shows the use of a variable to automatically customize thenotification for the associated event in accordance with someembodiments.

FIG. 23 shows a network manger UI environment for displaying upsellplans in accordance with some embodiments.

FIG. 24 shows a network manager UI environment for displayingpromotional notification plan in accordance with some embodiments.

FIG. 25 shows a network manager UI environment for displayingnotification templates (and associated device views) for defining a lackof capable plan (which may be combined with a offer for a upsell plan)for a desired service or application in accordance with someembodiments.

FIG. 26 shows a network manager UI environment for displayingnotification templates (and associated device views) for defining afeatured service or application in accordance with some embodiments.

FIG. 27 shows a network manager UI environment for displayingnotification templates (and associated device views) for defining afeatured service or application in accordance with some embodiments.

FIG. 28 shows a network manager UI environment for displayingnotification templates (and associated device views) to drag service orapplication up or down for presentation order (for example, priority,discover level, etc.) in a device in accordance with some embodiments.

DETAILED DESCRIPTION

As the number and types of services on a mobile device increase, itbecomes increasingly important to differentiate the services and typesof service to users in a way that users can easily understand, access,and launch. In some embodiments, device users can avail themselves ofone or more of bite-sized bulk data plans, application-specific dataplans, and sponsored data plans (for example, plans that are free to theend user because they are paid for by third party sponsors who makemoney when users use their over-the-top service or application).

FIG. 1 illustrates a management system 100 that supports service userdiscovery and service launch object placement on a device in accordancewith some embodiments. In some embodiments, the management system 100communicates with one or more mobile devices over a network 110 coupledto one or more of network service 120, application download server 140,device management system 170, and device 130. In some embodiments,device 130 includes a user interface (UI) location manager 132, a UIagent 134, a UI 136 and device services 138. In some embodiments, thedevice management system 170 includes a UI location management server150, a UI location management console 160 and an accounting database180.

In some embodiments, the management system 100 includes additional orfewer functions than those shown in FIG. 1. For example, in someembodiments, management system 100 does not include network service 120.In some embodiments, management system 100 does not include anapplication download server 140. In some embodiments, a devicemanagement system 170 does not include an accounting database. In someembodiments, a device management system 170 functionality is splitacross two entities, for example, a service provider and a third party.In some embodiments, the application download server 140 and the devicemanagement system 170 functions are combined. In some embodiments, theapplication download server 140 and the network service 120functionality is managed by the same entity (e.g., a service provider ora third party). In some embodiments, the device 130 does not includedevice services 138 or does not include UI agent 134. In someembodiments, two or more of the functionalities shown in FIG. 1 arecombined into a single function. For example, UI agent 134 and UIlocation manager 132 can be combined.

In some embodiments, the device management system 170 defines thelocation in a device UI 136 where a service launch object is placed toaid in managing the manner in which a user discovers the network service120 or device service 138 (for example, an application) and launches it.In some embodiments, the UI location manager 132 uses informationassociated with a service launch object (for example, metadata) toinstruct the UI agent 134 where to locate the service launch object inthe device UI 136.

In some embodiments, a UI location management service provider entityutilizes the apparatus shown in FIG. 1 to increase (for example, tooptimize) the discovery level for one or more service launch objects ona device or a group of devices with UI location (for example, placement)and notification messaging functions managed by a device-based UIlocation manager 132. In some embodiments, a device-based UI locationmanager 132 is further managed by the device management system 170. Insome embodiments, the UI location management service provider is acarrier (for example, a network access carrier or a service provider) ofaccess services who has control of the UI location management system. Insome embodiments, the carrier of access services may be a network accesscarrier (for example, a wireless network carrier such as Vodafone,Verizon, or AT&T, or a cable network carrier such as Comcast, etc.). Insome embodiments, the UI location management service provider is a thirdparty who provides the location management (for example, an applicationstore or marketplace provider such as Apple or Android/Google, a searchservices entity such as Google or Bing, or a third party UI locationmanagement entity, etc.). In some embodiments, the third party whoprovides the location management does not control or own the networkaccess assets (for example, an application store or marketplace providersuch as Apple or Android/Google, a search services entity such as Googleor Bing, or a third party UI location management entity, etc.). In someembodiments, it is advantageous for a carrier or applicationstore/marketplace provider to be the UI location management serviceprovider. In some embodiments, an entity that controls the UI locationmanagement system shown in FIG. 1 controls the UI location managementservice and therefore controls the discovery level for one or moreservice launch objects on one or more device 130. In some embodiments,device 130 is part of a device group.

In some embodiments, service launch object is an object on a device UI136 that a user of device 130 or a network entity (for example, devicemanagement 170, service provider, carrier, etc.) can select (forexample, “click on,” “open,” “launch,” etc.) to initiate a networkservice 120 or device service 138. In some embodiments, the networkservice 120 or device service 138 is a service or an application. Insome embodiments, initiating network service 120 or device service 138provides (for example, by launching, initiating, streaming, playing,presenting, displaying, purchasing, downloading, or preloading) acontent (for example, a video or movie or audio), or a software, or asoftware download, or software update. In some embodiments, selection ofthe service launch object initiates the network service 120 or deviceservice 138 by launching an application that is associated with theservice launch object; or directing an application (for example, as abrowser or portal application) to a particular network destination thatis associated with the service launch object; or opening a folder withone or more additional service launch object choices for the user toselect from; or providing the user with a notification regarding servicestatus or service plan permissions for this service; or providing theuser with payment or service account configuration options to enable theservice. In some embodiments, selection of the service launch objectinitiates the network service 120 or device service 138 by launching apurchase experience or a purchasing environment. In some embodiments,selection of the service launch object initiates providing a user ofdevice 130 with means to download an application from the applicationdownload server 140 and launch the network service 120 or device service138. In some embodiments, the service launch object is an Android “APK”(i.e., an application package) comprising an application and additionalassociated information, for example, information about an icon (forexample, a graphic or location) associated with a service or anapplication. In some embodiments, a service launch object icon is one ormore of a graphic, a text string, a UI user entry field or any othermeans for the user to choose to activate a service launch object.

In some embodiments, service launch object discovery level refers to thelevel of priority a service launch object receives relative to gainingthe device user's attention in order to encourage selection or launch aservice or application associated with the service launch object. Insome embodiments, a high discovery level corresponds to a premium UIlocation for the service launch object (for example, the service launchobject is placed in a prominent UI service launch partition, a homescreen, or a permanent launcher bar). In some embodiments, a highdiscovery level also includes or is indicated by one or more ofhighlighted service launch object icon features (wherein icon featuresinclude one or more of size, orientation, color, texture, persistence,transparency, foreground/background presence, skin, wallpaper, etc.) orprominent or frequent service launch object notification messages. Insome embodiments, a low discovery level is characterized by a lessprominent service launch object UI location or less prominent servicelaunch object notification messaging. In some embodiments, a lowdiscovery level includes one or more of: a service launch objectlocation in the device application stable, a service launch object on anapplication store/marketplace location, a service launch object withoutnotification messaging, and a one time notification message the firsttime the service launch object icon is displayed to the user.

In some embodiments, the management system provides for remotemanagement of location and modification of appearance for a servicelaunch object icon. In some embodiments, a service launch object icon isthe graphic shown on the device UI screen that represents the service orapplication (which may include a content or purchase experience)associated with the service launch object. In some embodiments, theservice launch object icon is positioned on a touch screen in thelocation that launches the service or application associated with theservice launch object when the user touches it.

In some embodiments, the management system provides for remotemanagement or modification of a service launch object notificationmessage. In some embodiments, a service launch object notificationmessage is a targeted user notification message that a user can observe(for example, see or hear) as associated with (or integral to) aparticular actionable service launch object because the service launchobject notification message is placed in, on, touching or in closeproximity to the service launch object icon. In some embodiments, thiskind of integral service launch object notification message requiresmanagement of how or when or where the notification message is displayedin the device UI. In some embodiments, the service launch object displaylocation is based on (for example, targeted for, or optimized for) eachservice launch object or must be mapped for each service launch objectand service launch object message pair. In some embodiments, associationof a notification message with an actionable (for example, “clickable”)service launch object icon on the device allows for targeted or specificuser messaging about various aspects of an available service orapplication in a manner that does not require the user to search for anicon to act on, nor does the user need to do further research on what anactionable icon offers the user experience. In some embodiments, anadvantage of the management system 100 is the remote management ofservice launch object notification messages that are (easily) recognizedor acted on by the user by virtue of the association of the notificationmessage and the actionable service launch object icon. In someembodiments, an additional advantage of the management system 100 isthat multiple notification messages for multiple actionable servicelaunch objects may be sent to the device (for presentation to a user)preventing the user from becoming confused about which service launchobject notification message goes with which service launch object.

In some embodiments, different types of service launch objects areplaced in a common device UI service launch partition in the device UI136 to aid the user in understanding that one or more service launchobject associated with network service 120 or device service 138represented in that UI service launch partitions are related or ofsimilar type. In some embodiments, the placement of the service launchobject within the UI service launch partitions is specified in thedevice management system 170. In some embodiments, the device managementsystem 170 provides a UI location where a service launch object isdesired to be placed, and the UI location manager 132 translates thatlocation into device UI 136 configuration to position the service launchobject icon in the desired UI location.

In some embodiments, multiple device UI service launch partitions areused to identify multiple groups of service launch objects. In someembodiments, the management system 170 specifies the one or more UIservice launch partitions in which a service launch object is to bedisplayed.

In some embodiments, the management system 170 specifies that a servicelaunch object is to be placed in a location on a device UI 136, with thelocation being one or more of a UI service launch partition, a devicemain screen, a device secondary screen, a device permanent launch area,a device application stable, a device file system location, anapplication download server, or other division.

In some embodiments, a network service 120 is sponsored on a user'sservice plan, and it is difficult or inconvenient for the user toremember the website and enter it. In some embodiments, the ability todynamically configure a device application (such as a browser, a portalapplication, a dedicated application such as a social networkapplication, a search application, a maps or location application, avoice or chat application, media streaming application, musicapplication, content viewing or purchase application, shoppingapplication, driving directions application, service plan selection orconfiguration application, service usage reporting application, a gamingapplication, a weather application, an email application, a widget, oranother service related application, etc.) with the proper destination,associate this configured application with a service launch object iconrepresenting the sponsored network service 120, and place the servicelaunch object icon in a convenient location on the device UI 136,provides the user with means to more easily “discover” or “launch” thesponsored network service 120. In some embodiments, a sponsored deviceservice 138 is difficult of inconvenient for the user to remember andthe management system performs one or more of the following: dynamicallyconfigure a device application with the proper destination, associatethis configured application with a service launch object iconrepresenting the sponsored device service 138, place the service launchobject icon in a convenient location on the device UI 136, provide theuser with means to more easily “discover” or “launch” the sponsoreddevice service 138.

In some embodiments, the service provider (such as a wireless carrier)may have a new service plan that the carrier desires the user to“discover” by trying. In some embodiments, the service provider couldconfigure a “try before buy” service plan wherein a “sample service”with shorter time span is provided or wherein the cost for service isless expensive for a period of time. The service provider can thenconfigure or place a service launch object in a location on the deviceUI 136 where the user is likely to discover it.

In some embodiments, the service provider (for example, a wirelessservice provider, application store or application marketplace serviceprovider, etc.) may provide means to specify where a given servicelaunch object is placed on a device UI 136, and charge the applicationprovider or service provider for the UI placement in accordance to thevalue of the placement. In some embodiments, placement in theapplication store or marketplace may be free. In some embodiments,placement in the on-device application stable might have lower cost,placement on one of the secondary device screens might be moreexpensive, placement in a UI service launch partition might cost evenmore, placement on the device main screen might be yet more expensive,and placement in the permanent launch area might be most expensive ofall. It should be understood that the actual hierarchy of pricing may beconfigured by the service provider. In some embodiments, the hierarchyof pricing is be configured by the service provider or the devicemanagement system 170.

In some embodiments, the device management system 170 includes anaccounting database 180 to associate the placement of a service launchobject on a device UI 136 with a billing rate for the applicationprovider or service provider or sponsor associated with the servicelaunch object.

In some embodiments, device UI discovery location is the portion of thedevice UI 136 that a service launch object reside in. In someembodiments, there is a single UI service launch partition (or folder ororganization) with service launch objects within it. FIGS. 2 through 7illustrate example embodiments with multiple partitions for servicelaunch objects. FIG. 2 illustrates a multiple partition UI servicelaunch partition where two or more types of services each have a UIservice launch partition that makes it clear to the user which type ofservice a given service launch object resides in. FIG. 2 shows atwo-partition UI service launch partition shown on a secondary devicescreen (e.g., the second device screen from the right as indicated bythe single dot on right and three dots on left). In FIG. 2, the servicelaunch object UI location specifies the partition or the location withinthe partition of several service launch object icons.

FIG. 3 illustrates a main device screen with service launch objects(labeled “Paid Data” and “Free Data”). FIGS. 4 and 5 illustratesecondary device screens accessible, for example, by selecting the “PaidData” and “Free Data” icons of FIG. 3. FIGS. 6A and 6B illustrate adevice “quick launch” or “permanent launch” UI area. FIG. 7 illustratesa device application stable. In addition, in some embodiments, servicelaunch objects reside in a device marketplace, application store,website or network server.

In some embodiments, the portion of the device UI reserved for one ormore service launch objects is identified by a differentiatingcharacteristic or attribute. In some embodiments, the differentiatingcharacteristic to identify the portion of the UI is defined by orcharacterized by one or more of: a color, a wallpaper, a transparency, awall, a window, a texture, and a border. In some embodiments, differentportions of a UI are classified into tiers (or, alternatively, classesor levels, etc.), and each of the classified sub-portions isdifferentiated by variations of one or more of: color, wallpaper,transparency, walls, windows, textures, borders, and a plurality ofscreens.

In some embodiments, the partitioned UI service launch partition portionprovides for two or more UI service launch partitions that indicate tothe user that the service launch objects in a given service launchpartition are members of a type of service. In some embodiments, aservice launch partition includes displaying user options for servicelaunch objects for “default” sponsored network services, websites,applications or content. In some embodiments, default sponsored networkservices, websites, applications or content are subsidized by a serviceprovider or third party. The term “default” refers to services that arepre-configured by a service provider, device original equipmentmanufacturer (OEM), operating system (OS) provider or third party. Insome embodiments, a service launch partition displays user options forservice launch objects for “user selected sponsored services,” whereinthe user selects from available sponsored service options and once theservice option is selected by the user then the service launch objectappears in the service launch partition. In some embodiments, the useris enabled to select a certain number of sponsored service options outof a larger list of sponsored service user options. In some embodiments,a service launch partition includes displaying user options for servicelaunch objects for paid services that the user has elected to sign upfor. In some embodiments, a service launch partition includes displayinguser options for service launch objects for services, sponsored or paid,that the user has not yet elected to sign up for but are available tothe user. In some embodiments, each of the two or more service launchpartitions in the multi-partition UI service launch partitionapplication (or widget) has text or graphics indicating to the user thetype of service for one of more of the multiple partitions. In someembodiments, the device UI discovery location is a UI location withinthe partitioned service object launcher, and the service launch objectUI location also specifies the partition or the location within thepartition.

In some embodiments, a service plan or a service component is specifiedin a service design environment (wherein the “service designenvironment” may include a service design center, a service designplatform, a service design management system, etc.). In someembodiments, the service design environment comprises associating thenetwork service 120 or device service 138 with one or more servicelaunch objects. In some embodiments, the service launch object includesone or more of an icon (graphic), a software application, a folder orsimilar collection of additional service launch objects, a networkdestination or a network communication end point, one or morenotification message sequences or information, and service selectionoptions. In some embodiments, the service design environment allows anentity to choose the device discovery UI location for the networkservice 120 or device service 138. In some embodiments, the devicediscovery UI location is one or more of service launcher application UI,partitioned service object launcher application UI, main device screenor a secondary device screen, quick launch area, permanent launch area,device application stable, device marketplace, application store,website or network server. In some embodiments, the service designenvironment allows the specification of where to preload an applicationif the application is not already loaded on the device 130 so that theapplication may be available the first time the user selects the networkservice 120 or device service 138. In some embodiments, thespecification is formatted into a set of instructions for a networkserver that communicates with the UI location manager 132 on the device130. In some embodiments, the set of instructions provides a servicelaunch object with configuration or placement or message informationthat instructs the UI location manager 132 on the device 130 where tolocate the service launch object in the device UI 136 or how toprovision the service launch object so that it properly launches orinstructs the user when the user selects the launch object. In someembodiments, the service launch object configuration or placement ormessage information can specify a network server destination where UIlocation manager 132 on the device 134 is to fetch one or more of therequired service launch object parameters.

In some embodiments, device 130 receives a service launch objectconfiguration or placement or message information from a network server.In some embodiments, device 130 identifies the portion of the servicelaunch object configuration or placement or message information thatspecifies the device UI 136 location for the service launch object. Insome embodiments, device 130 installs the service launch object icon inthe device UI 136 location. In some embodiments, device 130 associatesthe service launch object icon with the service launch object that willinitiate the network service 120 or device service 138 when the userselects the service launch object icon.

In some embodiments, the service launch object requires an applicationto launch the network service 120 or device service 138. In someembodiments, the device 130 is configured to search the availableapplications on the device 130, detect that a required application isnot present on the device 130 and preload it prior to the user selectingto launch the network service 120 or device service 138 associated withthe service launch object. In some embodiments, the device 130 isconfigured to detect that the required application is not present andthen automatically download the application when the user first selectsthe service associated with the service launch object. In someembodiments, the device 130 is configured to detect that the requiredapplication is not present on the device 130 and offer the user theoption to download the application when the user first selects thenetwork service 120 or device service 138 associated with the servicelaunch object. In some embodiments, wherein device 130 downloads orpreloads application, the device 130 can either download the applicationfrom a pre-defined application download server 140 or can download itfrom a location specified in the service launch object placementinstruction message.

In some embodiments, the service launch object is further configured toinclude notification messages that are displayed to the user when theuser selects or first selects the service launch object icon. In someembodiments, the notification message includes information on how muchthe service costs or what the service allowances are. In someembodiments, the notification message involves service plan selectionoptions that allow the user to elect to pay for a service, or allow theuser to select a sponsored service. In some embodiments, notificationmessages may be handled by a UI agent 134.

In some embodiments, the UI location manager 132 automatically populatesone or more of the service launch object, service launch objectassociated application, network destination specification or servicelaunch object icon in the proper location in the device UI when userselects the network service 120 or device service 138.

In some embodiments, device network state information is used to definethe state of one or more networks 110 that the device 130 is connectedto. Network state information includes one or more of the type of accessconnection to the network (for example, 4G wireless, 3G wireless, 2Gwireless, WiFi, cable, DSL, hot spot service provider, home LAN,corporate LAN, etc.), the list of available networks (for example, WiFiand 3G, or 4G and corporate LAN, etc.), time of day, home vs. roamingcarrier service provider status, network access cost (for example,service plan details and status), network congestion state, networkquality-of-service (QoS) state, device data rate, device signal quality,and any other characteristic of the network.

Device usage state information (wherein information could comprise oneor more of parameters, logs, history, etc.) provides information on themanner in which the device is used (for example, in the past, present orpredicted future) by the device user. In some embodiments, device usagestate information includes one or more of: the current or past state ofservice usage for one or more services, current or recent states ofapplication usage for one or more selected applications, current orrecent geographic locations, current or recent location searches,current or recent network destination history (websites, services,content, search terms, etc.), one or more applications currently beinginteracted with by the user, the current or recent network state, howlong it has been since the user pressed one or more UI feedback elementson the device, whether an application is running in the foreground orbackground, etc. In some embodiments, the device can collect deviceusage state information (for example, collected by the UI locationmanager 132, or some other device agent). In some embodiments, thedevice usage state includes device cognitive state, wherein the devicecognitive state includes information the device gathers from theenvironment based on the device sensors. In some embodiments, the deviceuses one or more of a camera, a microphone, a GPS, a motion sensor, agyroscope, a accelerometer, a temp sensor, a touch sensor, a humiditysensor, to determine the device state relative to the environment or theuser of the device. In some embodiments, the service launch objectmanagement (for placement, discovery level, notification message,bidding, etc.) is dynamic based on one or more of: device orientation(landscape vs. portrait vs. flat on a horizontal surface) or devicedistance or relative position to a user (near the head, in one or twohands, on a table, on the seat of a moving car, in the pocket of theuser, indoors/outdoors, etc.) or ambient light/noise levels orcomponents. In some embodiments, the device cognitive state is used todecide between a visual or audio or vibration notification or aspecialized target bid population or to bill for a service launch objectplacement or associated service or application usage. In someembodiments, the service launch object management is based in part onthe power state of the device, for example, powered up, active, screensaver, hibernate, sleep or powered down mode. In some embodiments, theservice launch object management changes the power state (for example,from screen saver to active) to increase awareness of an associatedservice or application to a user. In some embodiments, the user maydisable the power state change mode. In some embodiments, the servicelaunch object management is based on the power mode (e.g., whetherplugged in or battery-powered) or the state (percentage or timeremaining) of the battery charge.

In some embodiments, device-based usage information is communicated witha network element for further processing or analysis to determine how toenhance (e.g., improve, increase, optimize, etc.) discovery level forone or more service launch objects. In some embodiments, device usagestate information is collected by network elements and aggregated in thedevice management system 170 databases for further processing oranalysis to determine how to enhance discovery level for one or moreservice launch objects. In some embodiments, device usage stateinformation consists of a combination of information collected by thedevice and information collected by the network for further processingor analysis to determine how to enhance discovery level for one or moreservice launch objects.

In some embodiments, the availability of a network service 120 or deviceservice 138 is dependent on the network state of the device 130. In someembodiments, if the network service 120 or device service 138 isavailable for a current network state the service launch object icon isdisplayed in the specified UI location. In some embodiments, if thenetwork service 120 or device service 138 is not available for thecurrent network state the icon is not displayed. In some embodiments,the service launch object configuration or placement or messageinformation contains information that is a function of network state. Insome embodiments, and the UI location manager 132 uses the servicelaunch object configuration or placement or message information andnetwork state information to instruct the UI agent 134 to display theservice launch object icon in a given location in the device UI 136 in afirst network state and instructs the UI agent 134 to not display theservice launch object icon in a second network state.

In some embodiments, a UI location management console 160 provides anetwork manager a user interface environment for one or more ofcomposing the network state policies describing when one or moreservices are available, specifying whether to present a service launchobject (for example, display a service launch object icon), andspecifying whether to provide network state notification information onone or more service launch object icons. FIG. 21 shows a UI locationmanagement console 160 UI template for a network manager to define apolicy event notification to notify users (for example, to notify usersregarding one or more details of a service plan status, such as dataused (e.g., MB or GB used), percent of plan cycle used or remaining,plan expiration, etc.) in accordance with some embodiments.

In some embodiments, the availability of a network service 120 or deviceservice 138 is dependent on the network state associated with the device130, and if the network service 120 or device service 138 is availablefor a current network state then the service launch object icon isdisplayed with “normal” (or typical or standard) graphics features inthe specified UI location, and if the network service 120 or deviceservice 138 is not available for the current network state then the iconis displayed with graphics features that indicate the service is notavailable in the current network state. In some embodiments, instead ofor in addition to modifying the service launch object icon graphicsfeatures to indicate the network service 120 or device service 138 isnot available in the current network state, a notification message maybe overlaid on the service launch object icon, with the messageproviding information indicating that the network service 120 or deviceservice 138 is not available in the current network state.

In some embodiments, the service launch object configuration orplacement or message information contains one or more of icon versions,icon placements, or network state messages, that are a function ofnetwork state, and the UI location manager 132 provides the appropriateone or more icon version, icon placement, network message to the UIagent 134 to modify the associated service launch object icon as thenetwork state changes.

In some embodiments, a network service 120 or device service 138 issponsored in a first network state and paid in a second network state.In some embodiments, a network service 120 or device service 138 issponsored in a first network state and paid in a second network stateand in the first network state the service launch object icon appears ina UI service launch partition for sponsored services, and in the secondnetwork state the service launch object icon appears in a UI servicelaunch partition for paid services. In some embodiments, the servicelaunch object configuration or placement or message information containsplacement information that is a function of network state, and the UIlocation manager 132 uses this placement information to instruct the UIagent 134 to display the service launch object icon in a sponsoredservice location in the device UI 136 when the device 130 is in thefirst network state and instructs the UI agent 134 to display theservice launch object icon in a paid service location in the device UI136 when the device 130 is in the second network state.

In some embodiments, it is advantageous to show whether a service orapplication is free or paid by a feature differentiation directly on theservice launch object icon. An example embodiment of this is shown inFIG. 6B where the dollar sign represents paid services (for this exampleYouTube and Skype are paid services) and the dollar sign with a circleand line through it represents free (or sponsored) (for this exampleAmazon and Calendar are free).

In some embodiments, there is a permanent UI service launch partitionthat the user is not allowed to modify or remove from the device. Insome embodiments, the permanent UI service launch partition enables a UIlocation management service provider to enhance service launch object UIlocation, or service launch object icon appearance or service launchobject notification messages for one or more service launch objects. Insome embodiments, the UI location management service provider of thepermanent UI service launch partition allows the user to manage theapplications, folder and/or service launch objects that are located inother portions of the UI controlled by the user. In some embodiments,the user can control (for example, modify or alter or enhance) someparameters (for example, the ordering, or sorting, or formatting) ofservice launch objects within a UI service launch partition that is atleast partially controlled by a UI location management service provider.In some embodiments, the user can add or delete service launch objectsfrom a UI service launch partition that is at least partially controlledby a UI location management service provider. In some embodiments, theuser is not allowed to add or delete or control (for example, modify oralter or enhance) service launch objects contained in a UI servicelaunch partition that is controlled by a UI location management serviceprovider.

In some embodiments, the UI location manager 132 is instructed (orfollows a policy) to locate a service launch object in the UI based onthe current time (wherein current time could be based time of day, orday of week, or work/holiday, etc.).

In some embodiments, a policy is implemented on the UI location manager132 to specify that a service launch object is located in one area ofthe UI at a certain time of day or day of the week, and the servicelaunch object is re-located at another time of day or day of the week.As another example embodiment, rather than storing the time basedlocation policy on the device 130, the network (for example, the devicemanagement system 170) can instruct the UI location manager 132 tolocate one or more service launch objects in the UI based on time. Inrelated embodiments, other features of one or more service launchobjects are altered as a function of time including service launchobject appearance or features or service launch object notificationmessages.

In some embodiments, the UI location manager 132 is instructed (orfollows a policy) to locate a service launch object in the UI based onthe current network state. In some embodiments, a policy is implementedon the UI location manager 132 to specify that a service launch objectis located in one area of the UI for certain network states and servicelaunch object is re-located to another area of the UI for other networkstates. In some embodiments, the service launch object is located on thehome screen or in a prominent location in a UI service launch partitionwhen the device is connected to WiFi, 4G, uncongested, or high QoSnetworks. In some embodiments, the service launch object is re-locatedto a less prominent UI location, such as a secondary device screen, aless prominent location in the UI service launch partition, theapplication stable, or is not displayed at all when network statechanges to 3G, 2G, congested or low QoS or roaming network.

As another example embodiment, rather than storing the network statebased location policy on the device, the network (for example, thedevice management system 170) instructs the UI location manager 132 tolocate one or more service launch objects in the UI based on networkstate. In related embodiments, other features of one or more servicelaunch objects are altered as a function of network state includingservice launch object appearance or features or service launch objectnotification messages.

In some embodiments, the UI location manager 132 is instructed (orfollows a policy) to locate a service launch object in the UI based onthe device usage state information (for example, based on current, orpast, or predicted, or history, or logs of, device usage stateinformation). For example, a policy might be implemented on the UIlocation manager 132 to specify that a service launch object is locatedin one area of the UI for certain device usage state, and the servicelaunch object location is moved for other device usage state. In someembodiments, locate the service launch object on the home screen or in aprominent location in a UI service launch partition when the deviceusage state information (for example, based on application usage historyor user current activity) indicates (for example, based on estimates, orpredictions, or cost, etc.) that a given service offer is likely to beor interest to the user.

In some embodiments, the service launch object is located on the homescreen or in a prominent location in a UI service launch partition whenthe device usage state information recognizes a geographic area where aservice or retail opportunity is valuable or might be of interest to theuser, such as a nearby purchase opportunity.

In some embodiments, the service launch object is re-located to a lessprominent location in the UI service launch partition, to theapplication stable, or is not displayed at all when device usage stateindicates that the current device usage information (for example, basedon associated application history) is not related to the service launchobject or indicates (for example, based on estimates, or predictions, orcost, etc.) that a given service launch object is not likely to be orinterest to the user.

In some embodiments, the service launch object is re-located to a lessprominent location in the UI service launch partition, the applicationstable, or is not displayed at all when device usage state indicatesthat the current geographic location is not close to a retail purchaseopportunity associated with the service launch object.

In some embodiments, rather than storing the device usage state basedlocation policy on the device, the network (for example, the devicemanagement system 170) instructs the UI location manager 132 to locateone or more service launch objects in the UI based on device usagestate. In related embodiments, other features of one or more servicelaunch objects are altered as a function of device usage state includingservice launch object appearance or features or service launch objectnotification messages. In some embodiments, a service launch objectnotification message can alert the user when the service, content,purchase opportunity or application associated with the service launchobject is likely to be of interest to the user. In some embodiments,(which may be of interest to wireless access service providers), byusing one or more of a service launch object notification messages, aservice launch object UI location change or a service launch object iconchange (for example, a feature, size, orientation, persistence, etc.),the user of device 130 is made aware of additional access servicesavailable for trial or purchase. In some embodiments, (which may be ofinterest to wireless access service providers), by using one or more ofa service launch object notification messages, a service launch objectUI location change or a service launch object icon change (for example,a feature, size, orientation, persistence, etc.), the user of device 130is made aware of additional access services available for trial orpurchase based on the device usage state information (for example,history or logs) indicating that the user has been using accessservices.

In some embodiments, by using one or more of a service launch objectnotification messages, a service launch object UI location change or aservice launch object icon change (for example, a feature, size,orientation, persistence, etc.), the user of device 130 is made aware ofadditional access services available for trial or purchased based on thedevice usage state information (for example, history or logs) indicatingthat the user has been using access services in a manner that suggeststhe user may desire to try or buy additional access services at thepresent or future time.

In some embodiments, additional service launch object notificationmessages are provided for services, applications or content marketing,wherein the notification message is placed in, on, touching or in closeproximity to a service launch object icon (an icon proximity message),or wherein the notification message is located in a location in a UIdisplay in which the service launch object icon is contained (an iconcontainer message). In some embodiments, the notification messagesinclude one or more of the following objectives: informative, drawattention to a service launch object, market special offers for aservice launch object, provide service usage information for a launchobject, or indicate to a user that a service activation or servicepurchase is required to use a service associated with a service launchobject.

In some embodiments, marketing messages for an access service, anapplication, a content purchase, on-line shopping service, or anotherservice is placed directly on a service launch object icon, or closelyadjacent to a service launch object icon, or in a location in a UIdisplay in which the service launch object icon is contained (forexample, in service object launcher or a UI service launch partition),for the purpose of providing a convenient way for the device user tolearn that the service or application associated with the service launchobject icon is available or is available with special advantageousconditions or economics.

In some embodiments, the appearance of a service launch object icon ismodified to enhance or downgrade the discovery level. In someembodiments, enhancing or downgrading the discovery level isaccomplished by one or more of changing the service launch object iconfeatures, changing the icon graphic, overlaying the service launchobject icon graphic with a second icon or graphic, or merging the icongraphic with a second icon graphic. In some embodiments, the iconfeatures or the color scheme are changed in accordance with servicelaunch object icon UI management policy or instructions from thenetwork. In some embodiments, the service launch object icon is made toalternate in appearance (for example, flash or change colorsperiodically or “bounce” or “wobble” etc.) according to service launchobject icon UI management policy or instructions from the network.

In some embodiments, additional service launch object notificationmessages as described above are managed by the device management system170. In some embodiments, additional service launch object notificationmessages as described above are managed by the device management system170, wherein a service launch object and one or more of associatedapplication, network destination or other policy information, areassociated with a service launch object notification message. In someembodiments, additional service launch object notification messages asdescribed above are managed by the device management system 170, whereina service launch object and one or more of associated application,network destination or other policy information, are associated with aservice launch object notification message and the device managementsystem 170 then communicates the service launch object notificationmessage along with the other service launch object information asdescribed herein to the UI location manager 132; and the UI locationmanager 132 then displays the message in the appropriate UI location.

In some embodiments, the device management system 170 specifies the typeof service launch object notification message or service launch objectUI location; the type of message or UI location information iscommunicated to the UI location manager 132; and the UI location manager132 displays the message in the proper format in the specified UIlocation. In some embodiments, the device management system 170specifies the type of message or UI location of the service, applicationor content marketing message; the type of message or UI locationinformation is communicated to the UI location manager 132 along withthe other UI location manager 132 information described above; and theUI location manager 132 then displays the message in the proper formatin the specified UI location.

FIG. 8 provides three examples of proximity messages in accordance withsome embodiments. In FIG. 8 is an example of a multi-partition UIservice launch partition with three service launch partitions. A firstservice launch partition is for sponsored (e.g., free to the user)services and applications. A second service launch partition is forpre-paid services and applications. A third service launch partition isfor post-paid (for example, recurring) services and applications. Afirst example of a proximity message type is the bubble message on thepre-pay one-day service launch object icon that indicates: “SpecialOffer, 20% discount, Today only! !” A second example of a proximitymessage is the “Click for Free Trial” icon title message below theservice launch object icon for pre-paid email. A third example of aproximity message is the “Check This Out” message under the post-paid(recurring) Twitter service launch object icon.

In some embodiments, a service launch object notification message isplaced on or in a UI service launch partition UI area that has thecapability of displaying one or more service launch object notificationmessages for one or more service launch objects that are or will belocated in one of the UI service launch partitions. An example of thisaspect of the invention is shown in the example embodiment of FIG. 9,where the free Twitter access message and actionable icon is displayedon the UI service launch partition itself. In this embodiment theservice launch object will automatically populate in the free mobileaccess partition.

FIG. 10 shows example embodiments for elevating service or applicationdiscovery level with service launch object notification messages thatare conditioned on time (Amazon discount today only), geography(Opentable 50% lunch discount within one block) and a service launchobject notification that is not conditioned on time or geography(calendar connected application service—check out this new application).In some embodiments, one or more of the service launch objects in FIG.10 have been placed by the UI location manager 132 on the main devicehome screen as instructed by the device management system 170. In someembodiments, one or more of the service launch object in FIG. 10 areplaced by the user, and the UI location manager locates where the userhas placed the service launch object on the user device UI and thenplaces the service launch object notification message in associationwith the proper UI location. In some embodiments in which the user hascontrol of service launch object placement in the UI, the UI locationmanager locates where the user has placed the service launch object onthe user device UI and then modifies the appearance of the servicelaunch object icon as described herein.

FIG. 11 shows an embodiment wherein the service launch objects arelocated in the device application stable, and the UI location manager132 locates a service launch object and places the associated servicelaunch object notification message on that service launch object asdirected by the device management system 170. In the example of FIG. 11,the notification messages are “Check out this new app! !” for Facebookand “Free Maps Access for the next hour! !” for Google maps.

In some embodiments, a UI location management console 160 provides anetwork manager a user interface environment for performing the one ormore functions for composing service, application or content marketingor informative messages, associating the composed message with a servicelaunch object, or initiating the communication of the message content tothe device UI location manager 132.

In some embodiments, the UI location manager console 160 furtherprovides a user interface for specifying when the composed message is tobe displayed on the device. In some embodiments, the UI location managerconsole 160 further provides a user interface for specifying under whatnetwork state conditions the composed message is to be displayed on thedevice. In some embodiments, the UI location manager console 160 furtherprovides a user interface for specifying under what device usage stateconditions the composed message is to be displayed on the device.

In some embodiments, a variable is used to define notification messagesin a notification template to automatically customize the notificationfor the associated event. FIG. 22 shows the use of a variable (forexample, ${plan} to indicate a Name of service plan) to definenotification messages in a notification template (and associated deviceview) to automatically customize the notification for the associatedevent in accordance with some embodiments.

In some embodiments, a management console 160 UI provides a networkmanager a UI environment for displaying upsell plans. FIG. 23 shows anetwork manger UI environment for displaying upsell plans in accordancewith some embodiments. In some embodiments, a management console 160 UIprovides a network manager a UI environment for displaying promotionalplans. In some embodiments, a management console 160 UI provides anetwork manager a UI environment for displaying promotional service orapplication as a function of time (for example, daily, weekly or basedon a network or device or user state). FIG. 24 shows a network managerUI environment for displaying promotional notification plan inaccordance with some embodiments.

In some embodiments, a management console 160 UI provides a networkmanager a UI environment for displaying notification templates fordefining a lack of capable plan (for example, lack of data service plan,or lack of access to an application or content—for example, requiring aservice or application purchase) notification message for a desiredservice or application. FIG. 25 shows a network manager UI environmentfor displaying notification templates (and associated device views) fordefining a lack of capable plan (which may be combined with a offer fora upsell plan) for a desired service or application in accordance withsome embodiments.

In some embodiments, a management console 160 UI provides a networkmanager a UI environment for displaying notification templates fordefining featured service or application (for example) notificationmessage for a desired service or application. FIG. 26 shows a networkmanager UI environment for displaying notification templates (andassociated device views) for defining a featured service or applicationin accordance with some embodiments.

In some embodiments, a management console 160 UI provides a networkmanager a UI environment for displaying notification templates fordefining a promotional banner (or banner ad) for (or to promote ormarket) a service or application or a promotional banner for a servicelaunch object (or icon) associated with a service or application. Insome embodiments, the promotional banners notification templates includeone or more of a language, image, or associated plans. FIG. 27 shows anetwork manager UI environment for displaying notification templates(and associated device views) for defining a featured service orapplication in accordance with some embodiments.

In some embodiments, a management console 160 UI comprises a servicedesign center showing device UI launcher view. In some embodiments, theservice design center includes drag and drop icons. In some embodiments,selection of icons provides menus to components or plan view orsettings.

In some embodiments, the service launch object icon appearance ismodified to indicate the status of service usage for a service plan. Thestatus of service usage can be a graphic (such as a bar or gauge orhourglass or pie chart located on or near the service launch objecticon) or a numeric value signifying amount used, amount remaining,percent used or percent remaining, etc. (for example, relative to amonthly quota or cap). FIG. 12 provides several examples of suchembodiments. The service launch object icons in FIG. 12 are contained inthe UI in a three-partition UI service launch partition, with onepartition for service launch objects associated with sponsored servicesand connected applications, one partition for service launch objectsassociated with pre-paid services and connected applications, and onepartition for service launch objects associated with post-paid (orrecurring) services and connected applications. For example a servicelaunch object can represent a specific wireless access service accordingto a set of service classification rules and the service launch objecticon itself can display an amount (or percent or fraction) of serviceallowance consumed, or an amount of service allowance remaining. As amore detailed example embodiment, a pre-pay wireless service plan mayallow for a certain amount of open Internet data usage (often specifiedin megabytes or gigabytes), and a usage indication is provided on aservice launch object to indicate graphically how much usage isremaining or how much is consumed. An example is provided in FIG. 12 onthe pre-pay 100 MB service plan service launch object icon, with theicon showing that roughly 85% of the service plan limit is remaining and15% has been consumed. Another pre-pay example is shown in FIG. 12 wherethe Maps service launch object icon shows only approximately 10% of theservice limit remaining with 90% consumed. In some embodiments, theusage bar is displayed in a different color (e.g., the color changesfrom green to red) to indicate that the remaining service plan is lowand to encourage the user to purchase additional service soon (beforethe current service runs out). These example embodiments includedifferent service plan usage classifications—one for wide open Internetand the other specifically for maps. It will be appreciated that manyclassifications of service are possible, including classifications basedon a single application (e.g., Facebook), a single network communicationend-point (e.g., a destination), a group of applications (e.g., socialnetworking applications, such as Facebook and Twitter), a group ofnetwork communication end-points (e.g., several destinations), etc.

It will now be appreciated that if the two usage meters were providedonly in a UI screen format unrelated to the service launch object icons,then the user would need to open that UI screen, observe the usagestatus for each of the user's active services, and then remember theusage status later on when the user intended to act on one of theservice launch object icons by selecting that icon. In some embodiments,usage information is provided on the same screen that the user uses toact on the available services and applications. In some embodiments,usage information is provided on the same screen that the user uses toact on the available service launch object.

Further example embodiments for usage information displayed directly inassociation with a service launch object icon are provided in FIG. 12.For example, in FIG. 12 there is a limit to the amount of service usageavailable to the user in a given period of time for the sponsored (freein this case) services, and a user can easily see that the sponsoredtrial access is almost used up while there is still plenty of usageremaining for the Facebook and CNN services. In some embodiments, one ormore sponsored services have limited usage. In some embodiments, one ormore sponsored services (or any other service) have unlimited usage whenthat is the policy set by the network apparatus (for example, the devicemanagement system 170 or another network element). There are other paidrecurring service examples provided in the paid recurring servicespartition in FIG. 12, with various service plan usage classificationsand usage allowances, with allowances being based on a limit to theusage amount under the service plan classification or time based limits.

FIG. 12 also displays another embodiment for changing the appearance ofa service launch object icon to indicate that service has not beenpurchased or that additional service must be purchased before theservice or application may be used. For the embodiment in FIG. 12, theservice launch object icon appearance modification to indicate that theservice has not been purchased (or that additional service must bepurchased before the service or application may be used) is indicated bythe gas pump icon shown on the pre-paid one-day service and the post-pay(recurring) maps service. In some embodiments, the service applicationassociated with the service launch object has not been downloaded yetwhen the user first clicks on it (as could be the case when the fuelpump icon feature is displayed), then the application is automaticallydownloaded, or the user is given an option to download the application.

In some embodiments, service launch object icon modifications make iteasier for a user to identify one or more subsets of their one or moreservices or applications with plenty of service allowance remaining, ornear the end of their service allowance, or requiring an initial oradditional service purchase to use the service or application.

In some embodiments, usage information displayed on the service launchobject icon is obtained by the UI location manager 132 (or an some otherdevice agent), and the UI location manager 132 updates (for example,dynamically based on network state or device usage state) the servicelaunch object icon as described in detail herein by changing the icon,overlaying another graphic, merging with another graphic or overlaying anotification message.

In some embodiments, usage information for a given service launch objectis sent by a network element to the UI location manager 132 andformatted by the UI location manager 132 for display on the servicelaunch object icon. In some embodiments, usage information is collectedon the device 130 by the UI location manager 132 and formatted by the UIlocation manager 132 for display on the service launch object icon. Insome embodiments, usage information collected on the device 130 by theUI location manager 132 is synchronized with usage information fromnetwork element, then displayed on the service launch object icon. Insome embodiments, the usage information is displayed on the servicelaunch object icon for a one or more network states. In someembodiments, the usage information is displayed on the service launchobject icon when connected to a paid network (for example, 4G/3G/2G) butnot displayed for a free network (e.g., home WiFi). In some embodiments,the usage information is displayed on the service launch object iconwhen usage is above a threshold. In some embodiments, the usageinformation is updated when network state changes (for example, thedevice may be subject to different usage limits and/or usage levels for4G, 3G/2G, WiFi, home/roaming, etc.).

FIG. 13 displays a three-partition UI service launch partition inaccordance with some embodiments. The embodiment in FIG. 13 includes aservice launch partition for trial offers (for example, plans). In someembodiments, trial offers (wherein trial offers may be limited, forexample, time- or data-limited offers) contain service launch objectsassociated with services or applications that are available on a trialbasis. In some embodiments, trial offers comprise limited trial offers.In some embodiments, limited trial offers contain service launch objectsassociated with services or applications that are available on a trialbasis including one or more of the following limitations: for a periodof time (for example, limited time trial offers) or for a subset ofgeographies (for example, limited geography trial offers) or for asubset of networks (for example, limited network trial offers). In someembodiments, limited trial offers contain service launch objectsassociated with services or applications that are available on a trialbasis based on a limitation and are dynamically removed or swapped forother offers by the UI location manager 132. In some embodiments,limited trial offers contain service launch objects associated withservices or applications that are available on a trial basis based on alimitation and are dynamically removed or swapped for other offers bythe UI location manager 132 controlled by the device management system170 (for example, a UI location management service provider). This isanother embodiment for prominent discovery of services or applicationsthat a UI location management service provider desires to present to adevice user.

In some embodiments, one or more of the service launch object iconappearance, service launch object location or service launch objectnotification message change as a function of network state. FIG. 14shows an example embodiment where the device has entered the roamingstate and a service launch object notification message is displayed fora video streaming service that would be very expensive during roamingconditions. In some embodiments, a service launch object graphic featureis added according to the UI location manager policy or networkinstruction to highlight the roaming indicator on the device display(for example, the arrow in FIG. 13). In some embodiments, applicationsand services have varying degrees of roaming warnings (for example, nowarning at all) based on usage (for example, fewer or less obviousroaming warnings for low data usage or sponsored services orapplications) during roaming conditions. In some embodiments, sponsoredservice or application coverage by the sponsored service provider doesnot include roaming, and the user is notified. In some embodiments,sponsored service or application coverage by the sponsored serviceprovider does not include roaming, and the user is notified they willreceive roaming fees. In some embodiments, sponsored service orapplication coverage by the sponsored service provider does not includeroaming, and the user is notified of a request for a response from theuser (for example, by clicking or touching to select the service launchobject) acknowledging that using the service will result in roamingfees. In some embodiments, the user's response is stored by the devicemanagement system.

In some embodiments, the service launch object icon changes appearanceor color or animates to indicate a change in network state or servicecharges.

FIG. 15 shows a secondary notification message according to someembodiments. In some embodiments, a secondary notification message (forexample, a warning) is configured to be presented when a user chooses toactivate a service launch object under specific network state conditions(for example, while the device is connected to an expensive network, ora low performance network, or a low QoS network, etc.). In someembodiments, the secondary notification message (for example, warning)of the notification policy is managed by the remote device managementsystem 170 and the device UI location manager 132, and after the userselects (for example, clicks) the service launch object a secondnotification message is provided. In some embodiments, the secondarynotification message requires the user to (optionally) dismiss or acceptfor service launch object activation. In some embodiments, the secondarynotification message persists for a set period of time or until thenetwork state changes.

In some embodiments, the notification message is provided in a mannerthat does not interrupt service or application launch. In someembodiments, the service or application launch is held (for example,stalled or paused) until the user dismisses the message.

In some embodiments, the service launch object icon appearance, orservice launch object location is modified, or a service launch objectnotification message is presented based on a network state (for example,network QoS, network congestion, network performance, network bandwidth,network data rate or network signal quality). For the example embodimentin FIG. 17 the network QoS has been assessed (by a device agent or thenetwork) to meet a quality criteria (or alternatively to satisfycongestion criteria below a threshold or satisfy a data rate above athreshold or have high signal quality above a threshold) to supportstreaming voice over Internet protocol (VOIP) services. For the exampleembodiment in FIG. 17, the network state (for example, QoS, etc.) doesnot meet the criteria to provide good video service quality. In someembodiments, (for example, the embodiment in FIG. 17) the UI locationmanager 132 determines the network state level of quality (or receivesservice launch object network state messages from the network) andprovides targeted service launch notification messages to one or moreservice launch object.

In some embodiments, (for example, the embodiment in FIG. 17) the UIlocation manager 132 determines the network state level of quality (orreceives service launch object QoS messages from the network) andprovides targeted service launch notification messages to the VOIPservice launch object (Skype—good service) and the streaming videoservice launch object (YouTube—marginal service).

In some embodiments, service or application discovery level is elevatedby providing a service launch object notification message for an offer.In some embodiments, the offer is a limited offer. In some embodiments,the limited offer is a limited offer, wherein the limited offer isoffered over one or more of a limited time, limited geography, limitednetwork, limited devices, limited users. In some embodiments, theservice launch object associated with the offer may be in a UI servicelaunch partition or some other location on the device including a mainor home UI screen, or a secondary UI screen or some other UI area. FIG.18 shows an embodiment where the connected movie application (forexample, Netflix or iTunes) is displaying a service launch objectnotification message indicating that movie download is available at aspecial price during a limited time that the network is not typicallybusy. In some embodiments, the notification message is based on anetwork state that has sufficient capacity to allow less expensivedownloads (for example, WiFi, 4G, etc.).

FIG. 19 shows another example embodiment where the streaming videoapplication service launch object is indicating to the user a specialprice in the specific geographic location the device is in, with a timelimit in case the network becomes busy again later. In some embodiments,a service launch object notification message to increase discovery levelwith a notification message is conditional on multiple limitations (forexample, states or parameters). In some embodiments, a service launchobject notification message to increase discovery level with anotification message is conditional on multiple limitations one or moreof network state (for example, 3G in FIG. 19) and device usage state(for example, time of day and geographic location—“next 2 hours” and“this area” in FIG. 19).

It will now be clear to one of ordinary skill in the art that othercombinations of network state and device usage state parameters may beused to condition the occurrence and content of one or more servicelaunch object notification messages.

In some embodiments, a device user obtains service launch object usage(for example, network access service) allowance (for example, virtualcash, points, megabytes, etc.) by using services on the device whichgenerate revenue for the UI location management service provider or acustomer of the UI location management service provider. In someembodiments, a device user obtains service usage allowance (for example,virtual cash, points, megabytes, etc.) by using services on the devicewhich generate revenue for the UI location management service provideror a customer of the UI location management service provider. FIG. 20 isan example embodiment wherein a device user can gain access serviceusage allowance by using services on the device which generate revenuefor the UI location management service provider or a customer of the UIlocation management service provider. For example, in FIG. 20 the useris being informed by a service launch object notification message thatthey can now get free Skype service as a result of the usage points theyhave generated by using search services on the device.

In some embodiments, the UI location management service provider or UIlocation management service provider customer manages (for example,monitors or keeps track of) usage, visits, views, ad views, clicks, adclicks, or user purchase revenue generated by the device user's use ofservice or on-device purchases, and manages (for example, monitors orkeeps track of) of how many usage points (for example, point, virtualcash, megabytes, etc.) such events have generated for the user'saccount, and allows the user to convert the usage points into service orapplication usage (for example, access service) allowance for one ormore services or services plans. In some embodiments, management system100 counts service launch object interactions or banner ad views, couponclicks, etc. and gives credit for service or application, discountaccount, reward points or cash.

There are a number of ways the UI location manager 132 can be designedto accept the various information elements such as service launch objectinformation, application information, destination information, servicelaunch object notification messages, network state policies and usagestate policies as described herein, and use the network stateinformation and/or usage state information and/or notification messagesfrom the device management system 170 to re-locate service launchobjects (or icons) in the device UI, or to change the features orgraphics on the service launch objects, or to display different messagesin, on, touching or in proximity to the service launch objects. Severaldetailed embodiments are provided herein. An exhaustive list of allpossible embodiments for these functions is not practical and is oflimited value to one of ordinary skill in the art once the variousembodiments herein are understood. Armed with the teaching providedherein it will be clear to one of ordinary skill in the art how tocreate other design embodiments to accomplish the same functions.

It is also understood that the following embodiments for moving servicelaunch objects, modifying service launch objects, and providing servicelaunch object notification messages as a function of network state,device usage state or service launch object UI placement instructionsfrom the device management system 170 are taught individually, it isunderstood that these embodiments may be combined. For example, theembodiments for moving the service launch object icon to different UIlocations as a function of network state, device usage state or servicelaunch object UI placement instructions from the device managementsystem 170 can be combined with one or more of the embodiments forchanging the appearance of the service launch object icon or providing aservice launch object notification message. Similarly, embodiments forchanging service launch object appearance can be combined withembodiments for changing service launch object notification messages,and so on.

In some embodiments, wherein the UI locations of the service launchobject are changed as a function of various network states, the variousUI locations corresponding with the various network states are stored ina table managed by the UI location manager 132 which indexes the tableaccording to changes in the network state, when the network state changeis detected and the proper UI location is looked up with the networkstate index, and the service launch object is moved to new UI locationby the UI location manager 132.

In some embodiments, wherein the features of the service launch objecticon are changed as a function of network state, the various iconfeatures (for example, graphics files) and the current service launchobject UI location are stored in a table managed by the UI locationmanager 132 which indexes the table according to changes in the networkstate, when the network state changes is detected and the proper iconfeatures is looked up with the network state index, and the newlyfeatured service launch object icon is placed by the UI location manager132 on the device UI in accordance with the current service launchobject UI location stored in the table.

In some embodiments, the features of the service launch object icon arechanged as a function of network state, the various icon features (forexample, graphics files) for a network state overlay feature (whereinthe term overlay is used to include overlay, or superposition, or merge,or combine) and the current service launch object UI location are storedin a table managed by the UI location manager 132, and the table isindexed by network state, and when the network state change is detectedand the proper overlay icon graphic is used to overlay with a basic icongraphic on the device UI in accordance with the current service launchobject UI location stored in the table. In some embodiments, the overlayfeature may be obtained from a network element (such as the devicemanagement system 170) by the device (such as the UI location manager132) as described above. In some embodiments, the overlay feature may beobtained jointly by a network element (such as the device managementsystem 170) and by the device (such as the UI location manager 132) asdescribed above.

In some embodiments, the overlay is accomplished by the device (such asthe UI location manger 132), wherein the device 130 processes a basic(for example, standard) application icon or service launch object iconto perform the overlay of the basic icon with the overlay feature tobuild a new composite icon on the device. In some embodiments, theoverlay is accomplished by presenting the overlay graphics in, on or inclose proximity to the location in the UI containing the application orservice launch object icon, with the current service launch objectlocation being derived from the current service launch object UIposition in the aforementioned table.

In some embodiments, a service launch object icon (for example,including overlay feature) that changes as a function of network stateis obtained from a network element (such as the UI location managementserver 150), after the UI location manager 132 detects the network statechange and receives the new corresponding icon from the network element,the UI location manager 132 places the new icon in the proper servicelaunch object UI location.

In some embodiments, wherein a service launch object notificationmessage is changed as a function of network state, the various servicelaunch object notification messages that vary with network state and thecurrent service launch object UI location are stored in a table managedby the UI location manager 132 which indexes the table according tochanges in the network state. In further embodiments, after the networkstate change is detected and the proper service launch objectnotification message is looked up with the network state index, the newservice launch object notification message is used to replace theservice launch object notification message that was used in a priornetwork state, and the new service launch object notification message isplaced in, on, touching or in proximity to the service launch objecticon in accordance with the current service launch object UI locationstored in the table.

In some embodiments, a service launch object notification message thatchanges as a function of network state is obtained from a networkelement (such as the UI location management server 150), after the UIlocation manager 132 detects the network state change and receives thenew corresponding service launch object notification message from thenetwork element, the UI location manager 132 places the notificationmessage in, on, touching or in proximity to the service launch objecticon, with the new service launch object notification message beingplaced in the proper service launch object UI location by the UIlocation manager 132.

In some embodiments, wherein a service launch object notificationmessage is changed as a function of device usage state, the variousservice launch object notification messages that vary with device usagestate and the current service launch object UI location are stored in atable managed by the UI location manager 132 which indexes the tableaccording to changes in the device usage state.

In some embodiments, the device usage state change is detected and theproper service launch object notification message is looked up with thedevice usage state index, and the new service launch object notificationmessage is used to replace the service launch object notificationmessage that was used in a prior device usage state. In someembodiments, the device usage state change is detected and the newservice launch object notification message is placed in, on, touching orin proximity to the service launch object icon in accordance with thecurrent service launch object UI location stored in the table.

In some embodiments, an updated (for example, dynamic) service launchobject (for example, by changing one or more of service launch objectlocation, or service launch object icon, or service launch objectoverlay feature, or service launch object notification message, or UIservice launch partition message) that changes as a function of deviceusage state is obtained from a network entity (such as the devicemanagement system 170), when the UI location manager 132 detects thedevice usage state change and requests an updated service launch objectfrom the network element, and then the UI location manager 132 placesthe new service launch object at the appropriate UI location. In someembodiments, the device 130 keeps a device usage state log and providesto a network element (such as the device management system 170) one ormore of: the current state of service usage for one or more selectedservices, current or recent states of application usage for one or moreselected applications, current or recent geographic locations, currentor recent network destination history, current or recent applicationsbeing interacted with by the user, current or recent network state, howlong it has been since the user interacted on a UI feedback element onthe device; the device 130 receives from the network entity a newupdated service launch object (or index) to replaced the previousservice launch object and is placed by the UI location manager 132 inthe UI location corresponding to the new updated service launch object.In some embodiments, at least a part of the usage state information iscollected by the network entity. In some embodiments, at least a part ofthe usage state information collected by the device 130 is augmented bynetwork entity usage state information. In some embodiments; the devicemanagement system 170 receives the device usage state information fromthe device 130, including one or more of: the current state of serviceusage for one or more selected services, current or recent states ofapplication usage for one or more selected applications, current orrecent geographic locations, current or recent network destinationhistory, current or recent applications being interacted with by theuser, current or recent network state, how long it has been since theuser interacted on a UI feedback element on the device; and the devicemanagement system 170 performs one or more of the following tasks:process the usage state information to select services or applicationsmost advantageous to highlight to the user, or provide special useoffers to the user, or create service launch object notificationmessages for a services or application, or re-locating a service launchobject or updating (one or more of location, features, overlay, etc.) aservice launch object icon, or create a new set of service launch objectUI location instructions or placement policies for the device (forexample, for the UI location manager 132); and send the new set ofservice launch object UI location, updates, instructions or placementpolicies to the device (for example, the UI location manager 132).

In some embodiments, the device management system 170 receives from thedevice the device usage state information from multiple devices in adevice group (for example, multiple devices associated with a user, anenterprise, a family plan, etc.), including one or more of: the currentstate of service usage for one or more selected services, current orrecent states of application usage for one or more selectedapplications, current or recent geographic locations, current or recentnetwork destination history, current or recent applications beinginteracted with by the user, current or recent network state, how longit has been since the user interacted on a UI feedback element on thedevice; and the device management system 170 performs one or more of thefollowing tasks: process the usage state information to select servicesor applications most advantageous to highlight to one or more users ofthe device group, or provide special use offers to one or more users ofthe device group, or create service launch object notification messagesfor a services or application to one or more users of the device group,or re-locating a service launch object to one or more users of thedevice group or updating (one or more of location, features, overlay,etc.) a service launch object icon to one or more users of the devicegroup, or create a new set of service launch object UI locationinstructions or placement policies for the one or more devices of thedevice group (for example, for the UI location manager 132); and sendthe new set of service launch object UI location, updates, instructionsor placement policies to the one or more devices of the device group(for example, the UI location manager 132).

In some embodiments, an updated (for example, dynamic) service launchobject (for example, by changing one or more of service launch objectlocation, or service launch object icon, or service launch objectoverlay feature, or service launch object notification message, or UIservice launch partition message) is changed with a new service launchobject UI policy instruction received by the device UI location manager132 from a network element (such as the device management system 170).

In some embodiments, the UI location manager 132 or the devicemanagement system 170 update a service launch object (for example, bychanging one or more of service launch object location, or servicelaunch object icon, or service launch object overlay feature, or servicelaunch object notification message, or UI service launch partitionmessage) in order to change the level of user information or userattention gathering for one or more service launch objects.

In some embodiments, updating a service launch object in order to changethe level of user information or user attention is desired because a UIlocation management service provider desires to change the userdiscovery or marketing messages associated with one or more servicelaunch objects associated with one or more services or applications. Insome embodiments, updating a service launch object in order to changethe level of user information or user attention is the result ofpayments received by the UI location management service provider fromservice providers or application developers whose services orapplications are being highlighted in the new service launch object UIlocations, messages and discovery positioning. In some embodiments,updating a service launch object in order to change the level of userinformation or user attention is the result of the UI locationmanagement service provider benefiting directly from enhanced service orapplication usage by the user. In some embodiments, updating a servicelaunch object in order to change the level of user information or userattention is encourages the user to try new services or applicationsthat the user has not used before.

In some embodiments, updating (for example, dynamically modifying) aservice launch object (for example, by changing one or more of servicelaunch object location, or service launch object icon, or service launchobject overlay feature, or service launch object notification message,or UI service launch partition message) by the device management system170 is applied on one device at a time from a device group.

In some embodiments, updating (for example, dynamically modifying) oneor more service launch objects (for example, by changing one or more ofservice launch object location, or service launch object icon, orservice launch object overlay feature, or service launch objectnotification message, or UI service launch partition message) by thedevice management system 170 is applied on one device at a time in orderto enhance the user discovery of one or more services or applicationsare put in effect for one device at a time in accordance to a desiredimprovement in service launch object discovery for that device. In someembodiments, for updating service launch objects for device groups,payments received by a UI location management service provider are forthe device group and not just individual devices. In some embodiments,for updating service launch objects for device groups, payments receivedby a UI location management service provider are for the device groupand not just individual devices, and the payments are adjusted as afunction of how closely the device group information (for example,information derived from device usage state—history, logs, demographic,geographic, etc.) matches the desired device group information for theentity that is paying for enhanced service launch object discovery (orselection, or use, or clicks, etc.).

In some embodiments, the UI location management console 160 provides aweb portal (for example, an automated or secure web portal) forapplication developers to log in to set up sponsored services or devicediscovery levels for their applications or services. In someembodiments, the web portal provides a variety of options in variousembodiments, including but not limited to service launch objectdiscovery pricing that varies with one or more of: time per day or perweek or per month spent on a given discovery level; UI location;notification message type; notification message length, extent orcontent; notification message frequency; network state; device usagestate. In some embodiments, the web portal provides one or more of: iconupload for user designed icons, upload of user application orapplication specification for application store or marketplace download;network destination (for example, URL, domain, website, IP address,port, etc.) for a browser based service; etc.

In some embodiments, updating (for example, dynamic) one or more servicelaunch objects (for example, by changing one or more of service launchobject location, or service launch object icon, or service launch objectoverlay feature, or service launch object notification message, or UIservice launch partition message) by the device management system 170 inorder to enhance the user discovery of one or more services orapplications are put in effect in accordance to a desired improvement inservice launch object discovery for multiple devices that are part of adevice group. In such embodiments involving modifications to servicelaunch object UI discovery management for device groups, paymentsreceived by a UI location management service provider are for the devicegroup and not just individual devices, and the payments may be adjustedas a function of how closely the device group demographic information(for example, information derived from device usage state history)matches the desired demographics for the entity that is paying forenhanced service launch object discovery.

In some embodiments, the device management system 170 provides a biddingfunction for enhanced discovery of services or applications, whereinservice providers (for example, shopping service providers, locationbased advertising providers, on-line sellers of merchandise, contentproviders, access service providers, streaming service providers, socialnetwork service providers, Internet search service providers, etc.) orapplication developers (developers of applications who whish theirapplications to be highlighted to device users) are provided with abidding mechanism to bid on service launch object UI location placement,features and/or service launch object notification messages. In someembodiments, the device management system 170 provides a biddingfunction for enhanced discovery of services or applications, whereinservice providers or application developers are provided with a biddingmechanism to bid on service launch object UI location placement,features and/or service launch object notification messages, wherein thehighest bidder receives the service discovery position being bid upon.

In some embodiments, the device management system 170 provides a biddingfunction for enhanced discovery of services or applications, whereinservice providers or application developers are provided with a biddingmechanism to bid on one or more service launch object properties:placement, icon features, icon overlay, icon format, notificationmessages. In some embodiments, the device management system 170 providesa bidding function for enhanced discovery of services or applications,wherein service providers or application developers are provided with abidding mechanism to bid on one or more service launch objectproperties: placement, icon features, icon overlay, icon format,notification messages as a function of one or more of: network state,device usage state, user state. In some embodiments, the devicemanagement system 170 provides a bidding function for enhanced discoveryof services or applications, wherein service providers or applicationdevelopers are provided with a bidding mechanism to bid on one or moreservice launch object properties: placement, icon features, iconoverlay, icon format, notification messages as a function of one or moreof: network state, device usage state, user state, wherein the highestbidder receives the service discovery position being bid upon. In someembodiments, service launch object are classified based on UI location,icon features or service launch object notification messages into“service or application discovery levels,” wherein the premium levels ofservice discovery in general earn higher bids. Some embodiments involveclassifying the service launch object UI location, icon features orservice launch object notification messages into “service or applicationdiscovery levels,” wherein the premium levels of service discovery ingeneral earn higher bids. In some embodiments, a higher discovery leveltypically gains more attention from the user by having one or more of:more prominent service launch object UI location placement, morefrequent specific information regarding the service launch object, moreprominent service launch object notification messages. In someembodiments, a premium discovery level has the service launch objecticon placed in one or more of the following attributes: in firstposition in a permanent or prominent UI service launch partition, thedevice main screen, or a permanent launcher bar on the device, frequentservice launch object notification, frequent service launch objectnotification involving device usage state dependent analysis for when toprovide the notification messages. In some embodiments, a lowerdiscovery level would typically cost a bidder less, involves placementin the application stable of the device with little or no service launchobject notification messaging. In some embodiments, an in between (orintermediate or typical or standard) discovery level might include oneor more of the following attributes: non-permanent placement (forexample, the user can modify the placement or can remove the servicelaunch object icon from all but the application stable) in a UI servicelaunch partition or a secondary device screen, notification messagingtaking place only at certain times of day or certain geographiclocations.

In some embodiments, device management system 170 (or alternatively aservice design center or UI location management console 160) presentsdevice UI view of discovery position on bidding interface. In someembodiments, device management system 170 presents device UI view oficon animation on bidding interface. In some embodiments, devicemanagement system 170 presents device UI view of coupon issue frombidding interface. In some embodiments, device management system 170presents device UI view of notification from bidding interface. In someembodiments, device management system 170 presents device UI view ofnotification animation or coupon animation from bidding interface.

In some embodiments, the device management system 170 supports staticpurchase of device UI discovery level via an automated secure portalinterface. In some embodiments, the UI location management console 160is configured as a secure web interface for remote terminals. In someembodiments, a remote terminal user can log into a user sign up systemwhere the users credentials and credit are established. In someembodiments, the user of the device management system 170 (for example,service provider or application developer) purchases pre-configureddiscovery levels at pre-configured pricing for pre-configured devicegroups.

In some embodiments, the device group information (for example,demographics, device parameters, device user parameters) are displayedto the user of the device management system 170 to help in determiningthe relative value of the various levels of discovery available. In someembodiments, the user of device management system 170 purchases one ormore of: a discovery level for a pre-determined period of time, or for apre-determined number of user service launch object views, servicelaunch object notification message views, or service launch objectclicks.

In some embodiments, the device management system 170 supports dynamicbidding and purchase of device UI discovery level via an automatedsecure portal interface. In some embodiments, the UI location managementconsole 160 is configured as a secure web interface for remoteterminals. In some embodiments, a remote terminal user can log into auser sign up system where the users credentials and credit areestablished. In some embodiments, the user of the device managementsystem 170 bids upon various device group discovery levels, with thewinning bidder purchasing that discovery level. In some embodiments, theuser of the device management system 170 bids upon various device groupdiscovery levels, with the winning bidder purchasing that discoverylevel for one or more of: a pre-determined period of time, apre-determined number of user service launch object views, servicelaunch object notification message views, or service launch objectclicks.

In some embodiments, the number of views or clicks or selections orusage are tracked by the device (for example, the UI location manager132) and reported to the device management system 170. In someembodiments, the number of views or clicks or selections or usage aretracked or estimated by the device management system 170, by eitherestimating the number of views as a function of time or by observingnetwork traffic, or by a combination of both.

In some embodiments, the device management system 170 is configured toallow a portion of the device UI (for example, a partition in a UIservice launch partition) to be controlled by a third party, such as anapplication store or application marketplace service provider, or asearch provider, or a location based services provider or a mobiledevice advertising provider. In some embodiments, the device managementsystem 170 is configured to allow a portion of the device UI (forexample, one or more partitions in a UI service launch partition) to becontrolled by a third party, such as an application store or applicationmarketplace service provider, or a search provider, or a location basedservices provider or a mobile device advertising provider for placementof service launch objects, for example, prioritized, ranked, displayed,tiered to enhance discovery of associated service or applications.

There are numerous other detailed embodiment examples for selling UIdiscovery levels to service providers, a third party, third partyservice providers, content providers, merchandise retailers orapplication developers, either with discovery levels that arepre-negotiated and fixed for a period of time or geography or device oruser population, or discovery levels that are bid upon in real time,that one of ordinary skill in the art will now understand. The teachingshere show how to devise embodiments that enhance the ability toadvertise services or applications by associating the marketing messagesdirectly with the location, appearance and notification informationdirectly associated with a service launch object or service launchobject icon.

In some embodiments, the UI location manager 132 (or some other deviceagent), or the device management system 170 evaluates a user's use ofservices in order to determine a new service plan or an alternateservice plan that the user might benefit from or be willing to purchase(an “alternate service”). In some embodiments, a user is currently usinga pre-paid hourly Internet access plan, and the user is using severalhours per day, and there is a less expensive post-paid recurring serviceplan, then the post-paid recurring service plan is identified as analternate service by service analysis algorithms in the UI locationmanager 132 (or some another device agent), or the device managementsystem 170. In some embodiments, a user is subscribed to a first serviceand the UI location manager 132 or the device management system 170identify a service launch object notification message that is associatedwith a service launch object for the alternate service, and the servicelaunch object message is communicated to the UI location manager 132 (ormight be pre-cached on the device for retrieval by the UI locationmanager 132), and the UI location manager 132 places the service launchobject notification message advertising an alternate service on, in,touching or near the service launch object corresponding to thealternate service.

In some embodiments, a user is subscribed to a first service and the UIlocation manager 132 or the device management system 170 identify aservice launch object notification message that is associated with aservice launch object for the alternate service, and the UI locationmanager 132 places the service launch object notification messageadvertising an alternate service on, in, touching or near the firstservice launch object.

In some embodiments, the UI location manager 132 manages the UIlocations contained in a UI service launch partition with one or morelaunch partitions for organizing or displaying service launch objects.In some embodiments, the UI service launch partition displays acontrolled version of a service launch object icon that is similar to a“standard” (e.g., generic or typical or normal) service or applicationicon (for example, the standard application icon that comes with anapplication delivered by conventional means such as application store ormarketplace, Internet download or device user load) that is available inother UI locations on the device controlled by the user.

In some embodiments, the UI service launch partition displays acontrolled version of a service launch object icon that is similar to astandard service or application icon (for example, that may be availablein other UI locations on the device controlled by the user) wherein thecontrolled service launch object icon that exists within the one or moreservice launch partitions in the UI service launch partition has anappearance within the UI service launch partition that is modifiable, alocation within the UI service launch partition that is modifiable, orhas service launch object notification messages applied within the UIservice launch partition as described herein.

In some embodiments, the service launch object icon appearancemodifications, location modifications or service launch objectnotification messages that are managed or applied within the UI servicelaunch partition are under the control of the UI location managementservice provider by means of the device management system 170 and the UIlocation manager 132 while the standard service or application icon thatis located outside the UI service launch partition is not modifiable bythe device management system 170.

In some embodiments, the UI service launch partition is an application,widget, OS library function or other software module that is installedin the OS or added to the OS (the “UI discovery management module”)installed on the device. In some embodiments, the UI service launchpartition is an application, widget, OS library function or othersoftware module that is installed in the OS or added to the OS (the “UIdiscovery management module”) installed on the device for the purpose ofmodularizing the software required to perform the device computingoperations, communication operations, UI display operations and otheroperations required to implement the UI location manager 132. In someembodiments, the UI location manager 132 is integral to or containedwithin the UI discovery management module that manages which servicelaunch objects are displayed to the user, the organization (whereinorganizing includes any or all of ordering, prioritizing, ranking,sorting, classifying, etc.) of the service launch object icons withinthe UI service launch partition (including which partition a givenservice launch object is displayed in, the service launch object orderwithin the partition, whether or not the service launch object is in thefirst display screen or the user has to scroll to see it, etc.).

In some embodiments, the UI discovery management module has pre-assignedUI location or UI graphic areas within the one or more service launchpartitions for displaying service launch objects. In some embodiments,in order to simplify the process of communicating service launch objectnotification messages or placing them with the correct service launchobject, each pre-assigned UI location or UI graphics area has theability to display one or more service launch object notificationmessage types in pre-configured locations or message formats, with theUI location manager 132 maintaining a table (for example, an array, amatrix, a look up table, etc.) or other means to identify which UIlocation or UI graphics area a given service launch object is located inso that when the service launch object notification message needs to bedisplayed it is placed in the correct UI location or UI graphics area.In some embodiments, placing service launch object in pre-assigned UIlocation or UI graphics area reduces the complexity of the modification,placement or notification messaging applied to one or more servicelaunch objects is simplified or the complexity of the UI location andnotification messaging management instructions that are communicatedfrom the device management system 170 to the UI location manager 132.

In some embodiments, service provider controlled UI launcher UIpartition has a background that is different from the device screenbackground. In some embodiments, service provider controlled UI launcherUI partition has a background that is different from the device screenbackground, wherein different is one ore more of color, texture, font,transparency, intensity, gray scale, etc. In some embodiments, serviceprovider controlled UI launcher UI partition has it's own background oris “opaque” to device screen background. In some embodiments,application or widget is “opaque” to screen background.

In some embodiments, service provider controlled UI launcher UIpartition is partially visible relative (for example, translucent) tothe background of the device screen.

In some embodiments, service provider controlled UI launcher UIpartition is not visible (for example, it is transparent or see-through)and takes on the same background as the device screen. In someembodiments, the UI launcher UI partition takes on the background of alive wallpaper or other animated screen type.

In some embodiments, application or widget is “transparent” to screenbackground. In some embodiments, transparent application or widget toscreen background is accomplished with a UI partition graphic that istransparent. In some embodiments, transparent application or widget toscreen background is accomplished with a UI partition graphic thatdetermines the screen background and uses it as the UI partitionbackground. In some embodiments, transparent application or widget toscreen background is accomplished with a UI partition that consists ofseveral individual launcher icons rather than an entire screen area.

In some embodiments, where the UI discovery management module is a OSlibrary function or other software module that is installed in the OS oradded to the OS for a group of devices the advantageous aspects of theinvention are included directly in the device OS. In some embodiments,wherein the UI discovery management module is a software application orwidget it may be downloaded (for example, “over the air” (OTA) or “overthe Internet”) by a user, or installed by a user, or installed by adevice OEM, or installed by a service provider or installed by a devicedistribution agent without the need to include it in the device OS. Insome embodiments, wherein the UI discovery management module is asoftware application or widget not included in the device OS, a downloadof the UI discovery management module provides the ability to controlthe service launch object icon appearance (for example, features,overlay etc.), location or notification messages in a controlled mannerwithin the UI discovery management module. In some embodiments, whereinthe UI discovery management module is a software application or widgetindependent (for example, optional or not integral or erasable withoutaffecting OS other operations) of the device OS, a download of the UIdiscovery management module provides the ability to control the servicelaunch object icon appearance (for example, features, overlay etc.),location or notification messages in a controlled manner within the UIdiscovery management module. In some embodiments, wherein the UIdiscovery management module is a software application or widget notincluded in the device OS, a download of the UI discovery managementmodule provides the ability to control the service launch object iconappearance (for example, features, overlay etc.), location ornotification messages in a controlled manner within the UI discoverymanagement module without the need to control other (including forexample, similar) application icons on the rest of the device that arecontrolled by the user. In some embodiments, a UI location managementservice provider manages the discovery of service launch objects withlittle or no need to undertake the complexities of device softwareintegration or OS software integration.

In some embodiments, a UI location management service provider, whereinthe UI discovery management module is a software application or widgetthat may be downloaded the complexities of OS software integration arereduced (for example, avoided).

In some embodiments, an organization screen is provided in the UIservice launch partition to provide the user with a list of UI servicelaunch partitions that the user can to choose from for displaying one ormore categorized (wherein categorized may also be classified, ranked,organized) service launch objects within one or more partitions withinthe UI service launch partition. In some embodiments, the organizationscreen provides a user the option to select from a one or more displayscreens that each consist of one or more UI service launch partitionthat organizes a categorization of service launch objects. In someembodiments, the organization screen provides a user the option toselect from a one or more display screens that each consist of one ormore UI service launch partition that organizes a categorization ofservice launch objects and upon selection the user is provided with acategorization screen. In some embodiments, the categorization screencomprises display screens that organize service launch objects for oneor more of: service plan types (have been purchased, available but havenot been purchased, sponsored, free, paid, pre-paid, post-paid,recurring, time based, usage based, trial offers, special offers, familyplan services, multi-device services, enterprise or work services,consumer services, etc.), services categorized by application type (forexample, music and video, news, browsing, voice and videocommunications, shopping, location services, live event services, onetime special event services, etc.), demographic based categorization(for example, work vs. play services, teen demographic services,pre-teen services, family services, etc.), etc.

In some embodiments, the organization screen displaying multiplecategorizations of service launch objects is the first screen the usersees (the UI discovery module “default” screen). In some embodiments,the organization screen is accessed by the user via a user action (forexample, a voice command, keep pad input, selecting the screen orclicking a UI button). In some embodiments, a organization screen may beprovided wherein the user may select from a set of options to displayone or more UI service launch partition categories on the default userpartition display in the UI service launch partition. In someembodiments, a user may select to display one or more service launchpartitions from: free services, pre-paid services and trial servicespartitions (or any other available service launch object categories)within the UI service launch partition. In some embodiments, a user mayelect not to display one or more of post-paid or recurring services (orany other available service categorization). In some embodiments, asubset of the service launch partitions are user selectable. In someembodiments, a subset of the service launch partitions are not userselectable. In some embodiments, a subset of the service launchpartitions are exclusively controlled by the device management system170 via the UI location manager 132. In some embodiments, a some of theservice launch partitions are user selectable while others arecontrolled by the device management system 170 via the UI locationmanager 132. In some embodiments, if too many service launch partitionsare available within the UI service launch partition for simultaneousdisplay to the user, then the UI service launch partition can providefor scrolling through the available service launch partitions.

In some embodiments, the UI discovery management module provides for analternative display of service usage for one or more service launchobjects wherein one or more service launch object identifiers (forexample, service launch object icon) are displayed along with a usageindication for the one or more service launch objects. In someembodiments, the UI discovery management module provides for analternative display of service usage, wherein the service usage iscategorized. In some embodiments, service usage is categorized byservice launch object. In some embodiments, service usage is categorizedby (or further broken down by) one or more of application, networkdestination, network communication end-point (e.g., source ordestination), application type, service type, network type, home vs.roaming, geography and service class.

In some embodiments, service or application discovery level (forexample, discovery position) revolve through a UI partition according toa service launch object priority. In some embodiments, one of more of: adiscovery level position or a discovery position range, a time indiscovery position, a percent of time in discovery position, number ofviews or clicks, etc. are specified. In some embodiments, notificationmessaging is specified as a percent of service launch object iconinteractions (for example, views, clicks, touches, voice commands,etc.).

In some embodiments, UI 160 manages at least a part of the device UI 136presentation. In some embodiments, UI 160 manages at least a part of thedevice UI 136 presentation wherein presentation comprises one or more ofview, display, format, number of screens. In some embodiments, UI 160manages at least a part of the device UI 136 view for one or more ofservice launch object UI location, service launch object notificationmessages, service launch partition, service object launcher, UIdiscovery, service launch object icon. In some embodiments, UI 160manages at least a part of the device UI 136 view for one or more ofservice launch object UI location, service launch object notificationmessages, service launch partition, service object launcher, UIdiscovery, service launch object icon based on user input (for example,user profile or preferences) or user behavior (for example, usagehistory or logs).

In some embodiments, UI 160 includes a console UI with view of device UI136 one or more screens. In some embodiments, UI 160 includes a consoleUI with view of device UI 136 service launch partition. In someembodiments, UI 160 includes a console UI with view of device UI 136 forarranging configurations for service launch partitions. In someembodiments, UI 160 includes a console UI with view of device UI 136 forarranging configurations of one or more of skins, branding, colorscheme, buttons and button arrangements. In some embodiments, UI 160includes a console UI with view of device UI 136 to drag and drop(wherein for all instances drag and drop may be exchanged for drag ordrop or move up or move down) of service launch object onto desiredlocation in UI location management console 160 device UI launcher viewfor accomplishing correct positioning of service launch object ondevice. In some embodiments, UI 160 includes a console UI to associateservice launch object icons with service launch object configurationelements.

In some embodiments, UI 160 enables drag and drop of service launchobject onto a desired location in UI 160 device UI launcher view toprovision the device with service launch object parameters. In someembodiments, UI 160 associates service launch object icons with servicepolicy elements in UI location management console 160.

In some embodiments, UI 160 enables drag and drop of service launchobject onto desired locations in UI 160 device UI launcher view todefine service plan or service plan component policies for the servicelaunch object.

FIG. 28 shows a network manager UI environment for displayingnotification templates (and associated device views) to drag a serviceor application up or down for presentation order (for example, priority,discovery level, etc.) in a device in accordance with some embodiments.

In some embodiments, UI 160 enables managing one or more of servicelaunch object UI location, service launch object notification messages,service launch partition, service object launcher, UI discovery, servicelaunch object icon as a function (or based on) network state, and deviceusage state.

In some embodiments, UI 160 defines a dynamic service launch object iconas a function of state, wherein the dynamic icon feature include one ormore of icon service launch object appearance, overlay, placement,notification messages, etc.

In some embodiments, UI 160 defines a dynamic service launch object iconas a function of state, wherein the state includes one or more ofnetwork state, device usage state, and user state.

In some embodiments, UI 160 defines icon appearance as a function ofnetwork state or device usage state by selecting an icon and a secondarynetwork state or device usage state screen to enter secondary appearancegraphics (for example, one or more of: a new icon, an icon overlay, iconsuperposition). In some embodiments, UI 160 defines icon notificationmessages as a function of network state or device usage state byselecting an icon and a secondary network state or device usage state toenter secondary notification messages (for example, one or more of: typenotification message text, select format, select graphics, selectbackground, select a message from a table, etc.). In some embodiments,UI 160 defines icon notification message type as a function of networkstate or device usage state by selecting an icon and a secondary networkstate or device usage state to enter secondary notification messages. Insome embodiments, UI 160 defines icon notification message type as afunction of network state or device usage state by selecting an icon anda secondary network state or device usage state to enter secondarynotification messages from one or more of: select notification messagegraphics background from drag and drop list, or enter new graphics, ortype in notification message or choose from pre-specified list.

In some embodiments, UI 160 defines UI device views as a function of OSversions or device type. In some embodiments, UI 160 defines UI deviceviews for a device group. In some embodiments, UI 160 defines UI deviceviews for a device group sharing notification messages or iconappearance. In some embodiments, UI 160 defines UI device views for adevice group includes one or more of: a configuration of launch objects,UI partitions, skins, branding, messages, etc. In some embodiments, UI160 defines UI device views for a device group includes selectingnotification messages or icon appearance from a common list.

In some embodiments, UI 160 includes a console UI “sandbox” fordevelopers to manage (for example, design, modify, update, select, pick)a service plan. The UI sandbox provides third parties or developers withat least a subset of the suite of service plan management toolsavailable to the service provider. In some embodiments, UI 160management of a service plan comprises defining discovery position ortime in discovery position.

In some embodiments, UI 160 management of a service plan comprisesspecifying time in discovery position based on a revolving percentage oftime. In some embodiments, UI 160 management of a service plan comprisesdefining time in discovery position based on a screen view percentage.

In some embodiments, UI 160 management of a service plan comprises adeveloper entering credit credentials. In some embodiments, UI 160management of a service plan comprises a developer billing based on moreof more of: discovery position, discovery time in position, discoverypercentage of time, number of views, number of clicks, notificationmessages (for example, one or more of frequency, period, duty cycle,dwell time, view refreshes, percentage, relationship with othernotification messages), purchase revenue share, analytics generatedmessaging.

In some embodiments, UI 160 management of a service plan comprises adeveloper billing based on revenue share. In some embodiments, UI 160management of a service plan comprises a developer obtaining analyticsgenerated messaging.

In some embodiments, management system 100 includes auto-download ofassociated service or application after UI launcher receives servicelaunch object.

In some embodiments, management system 100 includes auto-download ofapplication when UI launcher receives service launch object so that userdoes not have to do this through marketplace. In some embodiments, thedeveloper pays (or is billed) for auto-download of application orservice capability.

In some embodiments, if a service or application or website is blocked(e.g., the device is not authorized to use the application or access thewebsite under a current service plan or service policy), a notificationmessage (for example, a text string with the blocked message) ispresented that no plan is available to allow the service or applicationor website. In some embodiments, a button is provided to dismiss themessage. In some embodiments, a button is provided to manage (forexample, stop or stall or put into the background or kill) the serviceor application or website. In some embodiments, a button is provided tolaunch the user into an application management screen to manage (forexample, stop or stall or put into the background or kill) the serviceor application or website.

In some embodiments, the UI location management system is associated(for example, coupled) to an application store or marketplace. In someembodiments, when or after an application developer uploadsapplications, the application developer receives an offer to bid on oneor more of more of: discovery position, discovery time in position,discovery percentage of time, number of views, number of clicks,notification messages (for example, one or more of frequency, period,duty cycle, dwell time, view refreshes, percentage, relationship withother notification messages), purchase revenue share, and analyticsgenerated messaging. In some embodiments, when or after an applicationdeveloper uploads one or more applications, the application developerreceives an offer based on revenue share. In some embodiments, when orafter the application developer uploads applications, the applicationdeveloper receives analytics generated messaging.

In some embodiments, when or after an application developer uploadsapplications, the application developer receives an offer to bid on oneor more of more of: discovery position, views, time in position withpercentage, clicks, messaging frequency (time, view refreshes,percentage), icon animation, icon feature change, purchase revenueshare, analytics generated messaging.

In some embodiments, the management system 100 recognizes the service orapplication plans a user (or device) has, and the launcher has a buy up(or upsell) selection (for example, a button) that offers upgrades. Insome embodiments, the management system 100 recognizes the service orapplication plans a user (or device) have and the UI 136 has a buy upbutton that offers upgrades.

In some embodiments, an offer to buy-down (or downsell) is buried in(e.g., available through) a lower discovery screen.

In some embodiments, an offer to buy-down is buried in a lower discoveryscreen that has a larger number (including all) of service launch objectchoices and that the user has to discover through a multi-screennavigation.

In some embodiments, management system 100 includes a web applicationprogramming interface (API) and application to implement a serviceobject launcher widget. In some embodiments, management system 100includes a website to implement service object launcher widget.

In some embodiments, service launch objects are organized intocategories set by the UI location management server 150. In someembodiments, service launch objects are organized into categories set bythe device management system 170 as controlled by a service provider.

In some embodiments, the UI 136 is partitioned in areas of carrier (orservice provider) control only or user control only or shared carrierand user control.

In some embodiments, a service launch object assists or becomes adiscovery mechanism comprising one or more of the following: changingappearance of the service launch object based on carrier (whereincarrier could be a service provider or third party) control, placingnotification messages on, in or near service launch object under carriercontrol, duplicating (for example, with derivate or modified orenhanced) icons of standard application icons, where duplicate icons areunder carrier control and initiate other processes on the device (inaddition to or instead of launching the service or application),automatic appearance or addition or removal of launch objects in acategory, changing launch object categories, offering a marketingvehicle for application developers to market their services orapplications.

In some embodiments, a service or application developer makes a widget(to replace the standard service or application icon) that the serviceor application developer controls and uses it to market a service orapplication. In some embodiments, a plurality of service or applicationdevelopers make a widget to market a service or application. In someembodiments, a plurality of service or application developers share awidget by a third party to market a service or application. In someembodiments, a carrier or service provider or OEM desires to controlnetwork load or user attention (for example, so-called “eyeballs”). Insome embodiments, a carrier or service provider or OEM desires tocontrol network load or user attention by a shared widget to marketservices or applications. In some embodiments, management system 100provides a platform for a many (for example, a plurality of service orapplication providers) to one (shared device management system orapplication store or widget) to many (for example, a plurality ofdevices or users) marketing platform for one or more of: placenotification messages (for example, promotions) on service launch objecticons, move/add/delete service launch object icons, manage appearance oficons. In some embodiments, management system 100 provides a marketplacefor service or application developers or service providers to promotetheir service or application with a service launch object icon. In someembodiments, management system 100 provides a marketplace for service orapplication developers or service providers to highlight their icons inthe device discovery process.

In some embodiments, management system 100 provides service orapplication developer levels (where levels is equivalent to classes,categories, ranking, etc.). In some embodiments, management system 100provides service or application developers one or more levels, with eachlevel including one or more of the following features: place service orapplication in market place, monetize service or application use (forexample, charge by view, click, time, update rate, bandwidth, etc. orfor example, separate category for all application related traffic),positioning, amount of time/views/clicks in service discovery launcher,priority positioning, priority amount of time/views/clicks in servicediscovery launcher. In some embodiments, management system 100 offersservice or application developers charge by view or click at a givendeveloper or discovery level.

In some embodiments, a service launch object ad is the presence of theservice launch object icon in a managed system that controls the deviceservice launch object icon service discovery level. In some embodiments,ads are for a service or application on the device. In some embodiments,ads are associated to a plurality of applications. In some embodiments,an ad management system determines a service or application on device132 and provides an ad based on controlling the service launch object.

In some embodiments, the ad management system determines a subset ofservice or applications on device 132 and manages ads to multipleapplications at the same time. In some embodiments, the ad managementsystem advertising functionality comprises downloading the service orapplication, and highlighting the application on the UI.

In some embodiments, the ad management system presents the servicelaunch object icon as if the service or application had been selected,and initiates other processes in addition to launching the service orapplication when the service launch object icon is selected. In someembodiments, the ad management system presents the service launch objecticon as if the service or application had been selected, and initiatesother processes comprising recording the selection for one or more of:analytics, usage statistics, charging, providing service sign upnotification or usage notification (for example, “here are your optionsfor service to use this application” or a roaming warning), download theapplications, etc.

In some embodiments, ads are associated to a launch partition in, on, ornear the service launch object being advertised. In some embodiments, anad is placed directly on or next to the service launch object icon. Insome embodiments, an ad is placed in a banner (for example, a tickertape). In some embodiments, the device UI portion reserved for adsincludes several classified (or tiered or ranked) partitions for ads(for example, a plurality of tiered banners). In some embodiments, thedevice UI portion reserved for ads includes several classified (ortiered or ranked) partitions for ads (for example, a plurality of tieredbanners) and the ad management system places ads into each classifiedpartition based on one or more of network, device usage, device or userstate and desired discovery level. In some embodiments, the device UIportion reserved for ads includes several classified (or tiered orranked) partitions for ads (for example, a plurality of tiered banners)and the ad management system places (alternatively prioritizes) ads intoeach classified partition based on one or more of network, device usage,device or user state and desired discovery level and bids from one ormore ad providers.

In some embodiments, service launch object icon features are varied toincrease or decrease service discovery (for example, highlight one ormore apps, grey-down one or more apps). In some embodiments, adsassociated to service launch object have icon features other (forexample, different) than the icon features on the service launch objectitself.

In some embodiments, service launch object icons are made availableaccording to a priority policy. In some embodiments, a user controlsservice launch object presence or placement in certain device UI areas,and service provider controls presence and placement in other UI areas.In some embodiments, the device 130 has a permanent UI placement areathat user cannot remove or modify service launch object. In someembodiments, the ads are placed in a service provider controlled deviceUI area, and dynamically change placement (for example, rotate orround-robin based on a random or ranked method) for presentation to auser.

In some embodiments, management system 100 creates a service launchobject icon similar to or identical to the standard service orapplication icon. In some embodiments, management system 100 places theservice launch object icon in a UI discovery location or appliesnotification messaging on, in or near the standard service orapplication icon or modifies the service launch object icon appearanceaccording to a service discovery priority policy for that service launchobject.

In some embodiments, selecting the service launch object icon registersthe selection for one or more of the following functions: usage historylog, click charging, intercepting the service or application launch andproviding service notifications, downloading the associated service orapplication, launching the service or application.

In some embodiments, a list of device service or application areobtained (for example, a search by UI location manager 132) for ondevice screen or in application stable. In some embodiments, managementsystem 100 indicates that the service or application is on device to amarketing message management system. In some embodiments, the marketingmessage management system places service launch object icon for serviceor application in UI launcher. In some embodiments, the marketingmessage management system checks a device or user service plan status(for example, state) and if appropriate provides a marketing message tothe user for services associated with that service or application. Forexample the marketing message management system notices the device hasthe YouTube application installed but does not have a special mediastreaming plan in place, and generates the marketing message: “would youlike to learn more about a special media streaming plan service option?”

In some embodiments, the marketing message management system checks adevice or user service plan status (for example, state) and generates amarketing message to the user for services associated with that serviceor application and the marketing message management system sendsmarketing messages related to the service or application. In someembodiments, the marketing message management system enters informationof the device receiving the marketing message into a differentiateddemographics value database indicating that marketing messages for thatservice or application are more valuable when sent to that device. Insome embodiments, the marketing database charges more for sendingmarketing messages for that application to that device.

In some embodiments, interactions (responses, views, etc.) of a userwith marketing messages are entered into a demographics value databasefor analysis (for example, regression, model fitting, classification,etc.). In some embodiments, the marketing message management systemcharges more for sending marketing messages for service or applicationto devices associated (for example, correlated) with analysis databaseinformation. In some embodiments, UI location manager 132 receives (forexample, accepts) marketing message, finds service or application,places message on, in or near service or application.

In some embodiments, configuration or management of a UI launch area orother discovery management functions is performed by a device managementagent, for improved user experience response time (for example, as usercontrolled UIs).

In some embodiments, configuration or management of UI launch area orother discovery management functions is performed by a device managementagent, resulting in device software that is specific to a given OS. Insome embodiments, the device management agent (for example, UI locationmanagement 132) accepts policies from a policy server (for example, UIlocation management server 150) to define one or more of UI launcher:launch partition, service launch object classification, configuration,branding, device placement, icons, icon placement, icon features, iconoverlay, icon messaging, icon rotation, highlighting, messagingpolicies, icon launch processes.

In some embodiments, the device management agent (for example, UIlocation management 132) performs periodic update of service launchobject (for example, one or more of service launch object icon,placement, notification messages, classification), or update of servicelaunch object when user first clicks on portal widget. In someembodiments, the device management agent (for example, UI locationmanagement 132) downloads service or application (for example, if notavailable on device) via portal or portal instruction to download fromapplication store or marketplace. In some embodiments, the devicemanagement agent (for example, UI location management 132) comprisesdevice UI management policy instructions tied to UI location managementconsole 160 which configures all of above. In some embodiments, UIlocation management console 160 accepts manager input and provisionsdevice UI management policy instructions.

In some embodiments, the device management agent is assisted by a portalapplication and portal server API to define a part of policy on portalserver rather than managing all on device. In some embodiments, thisassistance provides an option for computation complexity sharing anddevice response time to user.

In some embodiments, the device management agent being assisted by aportal to define a part of a policy on a portal server results in lessOS-specific software on device or a longer UI response. In someembodiments, the device management agent being assisted by a portal todefine a part of policy on portal server results in considerableOS-specific software and slowed device responsiveness.

In some embodiments, the device management agent being assisted by aportal to define a part of policy on portal server (for example, UIlocation management server 150) to define one or more of UI launcher:launch partition, service launch object classification, configuration,branding, device placement, icons, icon placement, icon features, iconoverlay, icon messaging, icon rotation, highlighting, messagingpolicies, icon launch processes.

In some embodiments, the device management agent (for example, UIlocation management 132) being assisted by a portal to define a part ofpolicy on portal server (for example, UI location management server 150)performs periodic update of service launch object (for example, one ormore of service launch object icon, placement, notification messages,classification), or update of service launch object when user firstclicks on portal widget. In some embodiments, the device managementagent (for example, UI location management 132) being assisted by aportal to define a part of policy on portal server (for example, UIlocation management server 150) downloads service or application (forexample, if not available on device) via portal or portal instruction todownload from application store or marketplace. In some embodiments, thedevice management agent (for example, UI location management 132) beingassisted by a portal to define a part of policy on portal server (forexample, UI location management server 150) comprises device UImanagement policy instructions tied to UI location management console160 which configures all of above. In some embodiments, UI locationmanagement console 160 accepts manager input and provisions APIinformation.

In some embodiments, the management system 100 is website based andresults in minimal OS specific software on device or longer UI response.In some embodiments, the website-based approach provides lessOS-specific device software, but has a longer UI response.

In some embodiments, the website based management system 100 manages oneor more of UI launcher functionality: launch partition, service launchobject classification, configuration, branding, device placement, icons,icon placement, icon features, icon overlay, icon messaging, iconrotation, highlighting, messaging policies, icon launch processes.

In some embodiments, the website based management system 100 performsperiodic update of service launch object (for example, one or more ofservice launch object icon, placement, notification messages,classification), or update of service launch object when user firstclicks on portal widget. In some embodiments, the website basedmanagement system 100 downloads from application store or marketplace.In some embodiments, the website based management system 100 comprisesdevice UI management policy instructions tied to UI location managementconsole 160 which configures all of above. In some embodiments, UIlocation management console 160 accepts manager input and provisionsdevice UI management policy instructions.

In some embodiments, UI location management console 160 displays adevice view for manager (for example, carrier, service provider, thirdparty, service or application developer) to drag and drop icons or todrag and drop icons into discovery priority bin for one or more of thefollowing management location options: device management agent basedwith policy download, portal based with API server log in, or websitebased. In some embodiments, UI location management console 160 displaysdevice view for manager to specify messaging, or messaging taken fromsponsor sandbox or for manager to drags and drops icons into messagingfrequency policy bin for one or more of the management location options:device management agent based with policy download, portal based withAPI server log in, or website based.

In some embodiments, a policy to control (for example, one or more of:allow, block, warn, throttle, background, etc.) a service or applicationis combined with the policy to present (for example, display) of servicelaunch object (for example, through service launch object icon).

In some embodiments, after a service or application that is attempted isidentified, the application is offered as a service launch object in the“unpaid services,” “paid services,” or “free trial” offers. In someembodiments, when a user selects an unpaid service or application, aserve up service offer notification message is presented to the user. Insome embodiments, the service launch object icon is used to get the userto try or buy services. In some embodiments, the device shares with aserver that a service or application was attempted under a plan that didnot cover the service or application. In some embodiments, after thedevice shares with a server that a service or application was attemptedunder a plan that did not cover the service or application, the servercreates an offer notification message and instructs device to offerservice or application in free trial area of service UI. In someembodiments, after the device shares with a server that a service orapplication was attempted under a plan that did not cover the service orapplication, a service launch object icon associated with the service orapplication is included in launcher.

In some embodiments, statistics are collected on one or more topapplications tried but not paid for. In some embodiments, a user entersnew trial plan by hand.

In some embodiments, the device management system 170 highlights (forexample, with notification messaging) to devices where users have triedto install. In some embodiments, the device management system 170 or UIlocation manager 132 perform automated association of application withapplication specific policies and notification for free trial. In someembodiments, the device management system 170 or UI location manager 132perform automated association of application notification for a bulkbucket free trial (“click here for a free trial of a service plan thatwill allow ‘textstringxyz’ app”).

In some embodiments, user friendly services or applications increaserevenues by expanding data users or expanding data devices. In someembodiments, user friendly services or applications increase value forone or more of service providers, access carriers, OEMs, third partyover-the-top service or application providers, chipset providers and OSproviders.

In some embodiments, a device is configured for select or trial orsponsored data access prior to delivery to a user. In some embodiments,a device is configured for select or trial or sponsored data accessprior to delivery to a user, and the user does not need to configure orpay for partial service access. In some embodiments, basic device accessis sponsored right out of the box and the user does not need to doanything to activate service. In some embodiments, from this sponsoredout of the box condition, the user has certain “free” services that aresponsored by the service provider or third party. In some embodiments,the sponsored right out of the box devices include one or more of:sponsored website and application connection services, access to thecarrier store, a limited amount of application specific services andbulk Internet access services that are provided on a trial (or limitedor capped) basis. In some embodiments, the consumer is provided with anintuitive service or application user interface (for example, apermanent services discovery area on the device UI) where the user caninstantly select from any number of service plans that are configured bythe service provider.

In some embodiments, the arrangement of the permanent services discoveryarea on the device UI is OTA-configurable by the device managementsystem 170 controlled by the carrier. In some embodiments, theenforcement of the required network control, charging or notificationpolicies required to support service offerings, including one or more ofsponsored and paid service offerings, is OTA-configurable by the devicemanagement system 170 controlled by the carrier. This policy enforcementand configuration capability is far beyond anything else in the marketor on the drawing boards in the carrier network equipment world.

In some embodiments, over-the-top services or applications are monetizedby managing application or service discovery placement and advertising.In some embodiments, an over-the-top service or application for a devicegroup is sponsored, where the over-the-top service provider orapplication developer bids on earning a service discovery position fortheir service or application.

In some embodiments, a portion of the device home screen or otherportions of the device UI are remotely configured or re-configured as apermanent carrier controlled service or application discovery UIenvironment. In some embodiments, a portion of the device home screen orother portions of the device UI are remotely configured or re-configuredas a permanent carrier controlled service or application discovery UIenvironment (for example, dynamically or periodically or state based) byan OTA device management system 170. In some embodiments, an OTA devicemanagement system 170 configuration controls what the user can modifyand what they cannot.

In some embodiments, the service or application icons displayed in thepermanent discovery area are used to display a service or applicationlaunch opportunity the carrier wishes to provide the user.

In some embodiments, when the user selects a service launch object iconin the discovery area, the device inserts notification messages priorto, concurrently or after launching the service or application. In someembodiments, the notification messages include service plan offerscustomized to the service or application, service usage warnings (forexample, service or application uses a lot of data, or service orapplication causes high roaming costs, etc.), offers for a relatedservice or application, etc. In some embodiments, notification messagesassociated with a service launch object icon launch are OTA-configured.

In some embodiments, a network entity of management system 100 providesupdates to the service launch object management (for example, UIdiscovery, placement, notification message, etc.). In some embodiments,a network entity of management system 100 provides a partial (or full)software upgrade for managing a service launch object. In someembodiments, a network entity of management system 100 provides updatesto the policy or policy software or policy parameters associated with aservice launch object. In some embodiments, a network entity ofmanagement system 100 provides a policy software updates to device 130.In some embodiments, a network entity of management system 100 providesservice launch object management (for example, UI discovery policy)software updates to device 130. In some embodiments, a network entity ofmanagement system 100 provides a partial of full software upgrade(including new device software) to enable or update service launchobject management (for example, UI discovery policy) to device 130.

In some embodiments, the service or application icons are re-arranged(for example, dynamically re-classified, re-ranked, re-prioritized,re-sorted) according to a discovery priority policy set by the devicemanagement system 170. In some embodiments, the re-arrangement is staticbetween discovery policy updates between the device management system170 and the device. In some embodiments, the re-arrangement is dynamicbetween policy updates between the device management system 170 and thedevice, wherein the arrangement of the service or application ismodified periodically. In some embodiments, the re-arrangement is basedon one or more of: interactions (for example, how many views, clicks,selections, voice commands) of the user with the UI launch area, whetheror not the service launch object icon has been selected or a number ofselections, how much time has elapsed, the geography the device is in,the network the device is connected to, network state, the time of day,the applications the user has recently been using, the websites the userhas recently been using, cognitive state of the device, deviceparameters, user parameters (for example, profile, preferences), etc. Insome embodiments, each service launch object icon has a discoveryplacement priority policy so that some service launch object are alwaysdisplayed in a high discovery location, some service launch object areoften displayed in a high discovery location, and some service launchobject are rarely or never displayed in a high discovery location.

In some embodiments, a subset of service launch object icon within thelaunch area have a marketing message placed on it according to a servicediscovery policy. In some embodiments, the marketing message is definedby the service provider or entered into the service provider system bythe service or application sponsor.

In some embodiments, each service launch object icon has a messagingpriority policy so that some service launch object have frequentdiscovery messages, some service launch object have less frequentservice discovery messages, and some service launch object rarely ornever get service discovery messages. In some embodiments, the frequencyof service launch object discovery messages is based on one or more of:interactions (for example, how many views, clicks, selections, voicecommands) of the user with the UI launch area, whether or not theservice launch object icon has been selected or a number of selections,how much time has elapsed, the geography the device is in, the networkthe device is connected to, network state, the time of day, theapplications the user has recently been using, the websites the user hasrecently been using, cognitive state of the device, device parameters,user parameters (for example, profile, preferences), etc.

In some embodiments, management system 100 manages one ore more of:which or how many service discovery message the service provider wantsdisplayed on service launch object icon at a given time (for example,number of simultaneous messages, dwell intervals, time spacing, etc.),how many service discovery messages should be displayed as a function oftime, service discovery messages as a function of one or more: time ofday, geography, network state, device cognitive state, user state, userinteraction with the device, etc.

In some embodiments, the management system 100 locates a service launchobject that has been downloaded to the device by the user and placesservice launch object icons in the launch area. In some embodiments,placing user-downloaded service launch object icons in the launch areais advantageous when the carrier offers services associated with theservice or application that the carrier desires to promote. In someembodiments, this is advantageous if the service or application sponsoris willing to pay the carrier for increased discovery priority when theuser has downloaded the service or application.

In some embodiments, the management system 100 locates a user service orapplication that has been downloaded to the device, identifies thelocation in the UI where the service launch object icon has been placedby the user, and provide service or application marketing messages in,on, or near the service launch object icon. In some embodiments, amarketing message is defined by the service provider or entered into theservice provider system (for example, a service design center) by theservice or application sponsor.

In some embodiments, each service launch object icon defined by theservice provider or entered into the service provider system has amessaging priority policy so that some service launch object havefrequent discovery messages, some service launch object have lessfrequent service discovery messages, and some service launch objectrarely or never get service discovery messages.

In some embodiments, the frequency of service launch object discoverymessages is defined by the service provider or entered into the serviceprovider system and is based on one or more of: interactions (forexample, how many views, clicks, selections, voice commands) of the userwith the UI launch area, whether or not the service launch object iconhas been selected or a number of selections, how much time has elapsed,the geography the device is in, the network the device is connected to,network state, the time of day, the applications the user has recentlybeen using, the websites the user has recently been using, cognitivestate of the device, device parameters, user parameters (for example,profile, preferences), etc. In some embodiments, the service provider(or entered into the service provider system) manages one ore more of:which or how many service discovery message the service provider wantsdisplayed on service launch object icon at a given time (for example,number of simultaneous messages, dwell intervals, time spacing, etc.),how many service discovery messages should be displayed as a function oftime, service discovery messages as a function of one or more: TOD,geography, network state, device cognitive state, user state, userinteraction with the device, etc.

In some embodiments, the management system 100 locates a user service orapplication that has been downloaded to the device, identifies thelocation in the UI where the service launch object icon has been placedby the user, and overlays graphics or text or sounds (for example, amodified icon) in, on, or near the service launch object icon to provideone or more of: highlight the discovery level of the service launchobject (or associated service or application) to the user, indicatewhether the service or application can access the network (for example,wireless wide-area network (WWAN)) given the services available to theuser (for example, services the user has elected to pay for), indicatewhether the service or application is free or is charged to a userbucket, indicate whether the service or application currently has accessto the network (for example, WWAN or WiFi) or not (for example, roamingpolicies can be set up according to applications, network policies canbe set up according to application [4G, 3G, 2G, WiFi, etc.], QoS orcongestion policies can be set up according to applications, etc.).

In some embodiments, management system 100 is configured with a devicemanagement secure back-end portal controlled by the carrier.

In some embodiments, the management system 100 device management secureback-end portal has a sandbox capability that allows service orapplication sponsors (or developers) to log in and pay for, or bid onone or more of the service or application discovery services describedabove. In some embodiments, the system provides for bidding on discoverylocation, message frequency, views, clicks, etc.

In some embodiments, the user gets more control of the device UI whenthe user pays more (for example, buys up or purchases an upsellservice). In some embodiments, the user gets less control of the deviceUI in exchange for a service plan discount from the service provider. Insome embodiments, higher levels of service plan (for example, moreexpensive plans, or by accumulating rewards from service or applicationusage) provide higher levels of UI customization. In some embodiments,the user gets a discount or a sponsored service (for example, subsidizedservice or application access) in exchange for allowing the serviceprovider (or some other network entity, such as an application provider)to control the device UI. In some embodiments, the user receives adiscount on device service to turn over a UI portion or partition of thedevice.

In some embodiments, two or more network entities (for example, acarrier and an application developer) share the revenue for anover-the-top service. In some embodiments, two or more network entities(for example, carrier and application developer) share the revenue foran over-the-top service (for example, a service launch object associatedto a service or application or content), where one entity provides theservice, application or content and the other entity provides theaccess.

In some embodiments, the device UI changes as user changes service plan.In some embodiments, the device UI shows free service or applicationuntil the user tries the service or application. In some embodiments,after the user tries the service or application, the service launchobject shows entry level paid service or application. In someembodiments, after the user tries the entry level paid service orapplication, the service launch object shows upgrade service orapplication (for example, upsells). In some embodiments, if the usage ofservice or application (or revenue) falls back, the service launchobject shows a lower cost alternative (for example, free service orapplication again). In some embodiments, the management system 100change offered service launch object (or associated service orapplication) based on the available service launch object on the device.

In some embodiments, service plans are sorted from lowest to highestcost data plans based on (or normalized) a per unit time basis based ona number of previous weeks of usage. In some embodiments, only upsell(or buy up) service plans are shown in the sorted list.

In some embodiments, a user or network entity has several options forsponsored data and an auction (or bidding engine) selects the winningservice.

In some embodiments, a service or application provider bids for UIdiscovery or placement (based on priority, user demographics, networkstate, device usage state, device cognitive state) over one or moregeographies (for example, one or more area codes or cities) or over oneor more geography tiers (nationwide, statewide, regional, sub-regional,address plus radius). In some embodiments, higher geography tiersreceive a bid discount (for example, nationwide has a lower normalizedcost than statewide).

In some embodiments, the service launch object provides control of theservice or application. In some embodiments, the service launch objectintercepts and controls the service or application. In some embodiments,the service provider (or OEM) takes over the service or application byinstalling a service launch object associated to the service orapplication. In some embodiments, the service launch object is associateto multiple service or application and has a table of service orapplication with policy entries for one or more of the associatedservice or application. In some embodiments, the policies comprise oneor more of: hold launch, notify (user or network entity) of launch,acknowledge selection of service or application, launch service orapplication and log acknowledgement in customer care, notify in parallelto launch, block launch, block launch and notify user or network entity,notify, acknowledge (for example, log selection).

In some embodiments, the notification associated to the service orapplication associated to the service launch object comprise one or moreof the following types of notification: need a service plan, selectedapplication is expensive on this network, selected application isexpensive when roaming, an advertisement associated to service orapplication (typically in parallel, but could be in series), offeringalternate applications, offering related applications, offering relatedactivity, offering related merchandise, combine with location, state,etc. information. In some embodiments, the notification associated tothe service or application associated to the service launch objectcomprise informing a user of fraud. In some embodiments, the service isdiscontinued or discounted or service use is accelerated based on fraud.In some embodiments, the notification ranks service or applicationsaccording to what is about to run out. In some embodiments, thenotification ranks service or applications according to what is about torun out and give an option to click down.

In some embodiments, the service provider manages location managementservice or application (for example, access services).

In some embodiments, the service launch object icon is the standard(wherein standard could refer to the generic, normal or typical) icon,and the management system 100 provides one or more of UI placement,location discovery (for example, including selecting portions in one ormore UI partitions or tiers or classification) and network entity basedpolicies (or directly managed by network entity) for the standardapplication icon.

In some embodiments, a service or application is launched when a networkstate change occurs, an entity of management system 100 obtains usagecounts to determine that a service or application is in use, searchesthrough table (for example, for policy instructions associated toservice or application) associated with service or application in use,and enforces policy (for example, shut down service or application orkeep service or application operating and notify user in parallel). Insome embodiments, a network state changes after a service or applicationis launched, a subset of the service or application included in theactive table are forced to quit and to re-launch on new network state.

In some embodiments, for bidding on UI location (placement, discoverylevel, etc.) of service or application associated to service launchobject comprises a bid table. In some embodiments, the bid tableincludes one or more entries for: spots, graphics, text, animation perentry. In some embodiments, bid table entries have time service launchobjects. In some embodiments, bid table entries have a minimum timewindow. In some embodiments, bid table entries change with time of day.In some embodiments, bid table entries have entries change with deviceusage state. In some embodiments, bid table entries have entries changewith geo. In some embodiments, bid table entries include one or more of:bid on one or more spots, bid on one or more time service launchobjects, bid on one or more time of day, bid on one or more geos. Insome embodiments, the service launch object are swapped based on one ormore of: changes is geo, network state, device usage state, etc.

In some embodiments, the bid is for a pre-configured geo. In someembodiments, the bid is on geographic location (city, state, etc.) orzip with radius. In some embodiments, the user of bidding platform paysfor one or more of: per display, per unit time, or per click. In someembodiments, the base pay is for a unit time. In some embodiments,payment increased per view (for example, with a limit). In someembodiments, additional payment per click (for example, with a limit orcap). In some embodiments, pay increases for animation, etc.

In some embodiments, bulk buys (for example, discounts, rebates,coupons, etc.) are provider for large geographic areas (for example,nationwide). In some embodiments, bidder pays more for geographicspecific bids. In some embodiments, bids have TOD policies. In someembodiments, bids have device usage (or network) state policies. In someembodiments, table entry in a given geographic and time of day goes tohighest bidder. In some embodiments, the bid includes a minimum timewindow.

In some embodiments, bid winner algorithms as based on geographic level(for example, population or area size or level) selection relative tobid offer. In some embodiments, bidder screen provides selection ofgeographic areas to bid on and high bidder wins. In some embodiments,the highest nationwide bidder (for example, regardless of regional orlocal bidders). In some embodiments, regional highest bidder isconsidered if higher than a nationwide bidder by a target amount (forexample, percentage or threshold, etc.). In some embodiments, locationspecific bidder is considered if higher than a regional (or nationwide)bidder by a desired target amount. In some embodiments, a device usage(or network or device or user) state specific bidder is considered ifhigher than larger geographic bidders by a target amount. In someembodiments, a previous bid winner is shuffle down if knocked down byhigher bid (or higher by a give percentage or threshold) for higherposition. In some embodiments, the bid winner algorithm is based onmaximizing the revenue from bid pool or devices.

In some embodiments, bidding includes one or more spots including: spotfor search, spot for featured sponsored, spot for ads, spots forcoupons, spot for maps, etc. In some embodiments, the bidding includesbid types, for example, bid on specialized spots or bid on generalpurpose spots (for example, based on target user, or device, orgeographic location, or network state parameters). In some embodiments,select targeted time or geography or state rules for special spots (vs.general purpose spots). In some embodiments, the bidding platformincludes an area (or portion of device UI) for OEM customization. Insome embodiments, the bidding platform includes an area (or portion ofdevice UI) for user customization. In some embodiments, the area for OEMor user customization may be viewed on a service design center (SDC)screen.

In some embodiments, the portion of the device UI reserved for thelauncher is configurable (for example, left, center right, small,medium, large, upper, middle, lower). In some embodiments, the portionof the device UI reserved for the launcher is SDC or OTA-configurable.In some embodiments, the device is configured to include a UI menu forconfigurable discovery management display or launcher. In someembodiments, the device includes a default launcher, for example, for(first) power up, and then user can subsequently change. In someembodiments, the default launcher comes back every power cycle or comesback after a set time or comes back after sleep. In some embodiments,the return to default launcher is SDC or OTA-configurable. In someembodiments, the launcher configuration is viewable in SDC screen.

In some embodiment place a special identifier near the launcher (forexample, make a shim below launcher) so that launcher area is permanent.In some embodiments, the UI portion includes an enhanced launcher thatrecognizes permanent areas and gives user control of all other areaswhen they download the enhanced launcher.

In some embodiments, a user or network entity can drag icons fromlauncher to standard UI display (or screen). In some embodiments, theicons could be converted (or reverted) between real icons or speciallauncher icons. In some embodiments, the icons could be converted (orreverted) between real icons or special launcher icons when the iconsare dragged between the launcher and the standard UI display.

In some embodiments, a network system performs a method comprising:obtaining information to assist in identifying a plurality of portionsof a user interface of a wireless device, the wireless devicecommunicatively coupled to the network system over a wireless accessnetwork; obtaining an object placement policy, the object placementpolicy comprising a first set of one or more rules for identifying aparticular portion of the plurality of portions of the user interface ofthe wireless device in which to place one or more objects; determining adifferentiating attribute for the particular portion of the userinterface; obtaining the one or more objects; based on the objectplacement policy, determining configuration information, theconfiguration information at least configured to assist the wirelessdevice in placing the one or more objects in the particular portion ofthe user interface; and sending the configuration information to thewireless device over the wireless access network. In some embodiments,obtaining the object placement policy comprises obtaining the first setof one or more rules from a service design center. In some embodiments,obtaining the object placement policy comprises obtaining the first setof one or more rules from memory. In some embodiments, obtaining theobject placement policy comprises obtaining the first set of one or morerules from an entity associated with at least one of the one or moreobjects.

In some embodiments, at least one of the one or more objects is aservice launch object. In some embodiments, at least one of the one ormore objects is an advertisement.

In some embodiments, the first set of one or more rules is configured toestablish an ordering within the plurality of portions. In someembodiments, the plurality of portions includes a first portion and asecond portion, and the first set of one or more rules is configured toestablish the first portion as a higher priority portion than the secondportion.

In some embodiments, at least one of the one or more objects isassociated with one or more of a particular application program, aparticular service, a particular content item, and a particularadvertisement. In some embodiments, at least one of the one or moreservice launch objects is an icon. In some embodiments, at least one ofthe one or more service launch objects is a banner advertisement. Insome embodiments, at least one of the one or more service launch objectsis a particular icon for launching a particular application program. Insome embodiments, at least one of the one or more service launch objectsis a particular icon for launching a particular service. In someembodiments, at least one of the one or more service launch objects is aparticular icon for launching a particular content item. In someembodiments, at least one of the one or more service launch objectscomprises an advertisement. In some embodiments, at least one of the oneor more service launch objects is configured to launch a purchase offer.

In some embodiments, obtaining information to assist in identifying theplurality of portions of the user interface of the wireless devicecomprises obtaining the information from an entity. In some embodiments,the entity is an operator of the wireless access network. In someembodiments, obtaining information to assist in identifying theplurality of portions of the user interface of the wireless devicecomprises obtaining the information from memory. In some embodiments,obtaining information to assist in identifying the plurality of portionsof the user interface of the wireless device comprises obtaining theinformation from the wireless device. In some embodiments, obtaininginformation to assist in identifying the plurality of portions of theuser interface of the wireless device comprises obtaining theinformation from an entity associated with at least one of the one ormore objects. In some embodiments, obtaining information to assist inidentifying the plurality of portions of the user interface of thewireless device comprises obtaining the information from apre-determined configuration.

In some embodiments, the configuration information comprises a softwarebuild. In some embodiments, the software build comprises an update to auser interface software build.

In some embodiments, at least one of the one or more objects is aparticular icon configured to launch a particular software application,and the configuration information is further configured to assist thewireless device in associating the particular icon with the particularsoftware application.

In some embodiments, the plurality of portions of the user interfaceincludes a partition of a screen of the wireless device. In someembodiments, the plurality of portions of the user interface includes aparticular screen of a multi-screen user interface display. In someembodiments, the plurality of portions of the user interface comprises aplurality of partitions of a multi-screen user interface display. Insome embodiments, the plurality of portions of the user interfacecomprises a plurality of partitions. In some embodiments, the pluralityof partitions is classified based on ease of discovery to a user of thewireless device. In some embodiments, classifying comprises one or moreof prioritizing, ranking, ordering, sorting, and establishing tiers.

In some embodiments, at least one of the one or more objects isassociated with an entity comprising one or more of a user interfacelocation manager, an original equipment manufacturer, a carrier, anaccess carrier, a service provider, and an object provider.

In some embodiments, determining the differentiating attribute orcharacteristic of the portion of the user interface comprisesdetermining a characteristic to assist a user in identifying theparticular portion of the user interface. In some embodiments, thedifferentiating attribute comprises one or more of a border, a window, acolor, a wallpaper, a background, a texture, a transparency, and abrightness.

In some embodiments, the network system obtains information about anetwork state and obtains the one or more objects for placement in theparticular portion of the user interface by obtaining the one or moreobjects based on the information about the network state. In someembodiments, the network state is one or more of a network type, anetwork cost, a network service plan, a network latency, and a networkquality-of-service level. In some embodiments, the network type is oneor more of WiFi, cellular, home, and roaming.

In some embodiments, the network system obtains information about adevice state and obtains the one or more objects for placement in theparticular portion of the user interface by obtaining the one or moreobjects based on the information about the device state. In someembodiments, the device state comprises one or more of a current usagemeasure, a past usage measure, a current device location, a past devicelocation, a current user interaction state, a past user interactionstate, a current device cognitive state, and a past device cognitivestate.

In some embodiments, the network system obtains information about a userand obtains the one or more objects for placement in the particularportion of the user interface comprises obtaining the one or moreobjects based on the information about the user. In some embodiments,the information about the user comprises one or more of a user profile,a user preference, a current behavior, or a past behavior.

In some embodiments, the configuration information assists the wirelessdevice in preventing a user from modifying the particular portion of theuser interface or a contents of the particular portion of the userinterface.

In some embodiments, at least one of the one or more objects isassociated with a particular service or a particular application, andwherein the configuration information is further configured to assistthe wireless device in one or more of: enabling or launching theparticular service or the particular application when a user selects theobject, and providing additional management functions to the particularservice or the particular application when the user selects the object.In some embodiments, the additional management functions include one ormore of providing service usage information, allowing objectmodification, and providing object notification messages. In someembodiments, allowing object modification comprises allowingmodifications to one or more of object placement, object positioning,and object classification.

In some embodiments, the network system classifies the one or moreobjects, and the configuration information is based on theclassification of the one or more objects.

In some embodiments, the network system provides a view of the userinterface of the wireless device to a network system manager.

In some embodiments, identifying the particular portion of the userinterface of the wireless device comprises obtaining identifyinginformation from a service design center.

In some embodiments, determining the differentiating attribute of theidentified portion of the user interface comprises obtaining attributeinformation from a service design center.

In some embodiments, the network system obtains the one or more objectsfor placement in the particular portion of the user interface byselecting the one or more objects based on a second set of one or morerules.

In some embodiments, at least one of the one or more objects isassociated with a particular entity of a plurality of entities, andfurther comprising: obtaining bids from one or more of the plurality ofentities, including the particular entity; and identifying theparticular entity as a winning bidder.

INCORPORATION BY REFERENCE

This document incorporates by reference for all purposes the followingnon-provisional U.S. patent applications: application Ser. No.12/380,778 (Attorney Docket No. RALEP004), filed Mar. 2, 2009, entitledVERIFIABLE DEVICE ASSISTED SERVICE USAGE BILLING WITH INTEGRATEDACCOUNTING, MEDIATION ACCOUNTING, AND MULTI-ACCOUNT, now U.S. Pat. No.8,321,526 (issued Nov. 27, 2012); application Ser. No. 12/380,780(Attorney Docket No. RALEP007), filed Mar. 2, 2009, entitled AUTOMATEDDEVICE PROVISIONING AND ACTIVATION, now U.S. Pat. No. 8,839,388 (issuedSep. 16, 2014); application Ser. No. 12/695,019 (Attorney Docket No.RALEP022), filed Jan. 27, 2010, entitled DEVICE ASSISTED CDR CREATION,AGGREGATION, MEDIATION AND BILLING, now U.S. Pat. No. 8,275,830 (issuedSep. 25, 2012); application Ser. No. 12/695,020 (Attorney Docket No.RALEP024), filed Jan. 27, 2010, entitled ADAPTIVE AMBIENT SERVICES, nowU.S. Pat. No. 8,406,748 (issued Mar. 26, 2013); application Ser. No.12/694,445 (Attorney Docket No. RALEP025), filed Jan. 27, 2010, entitledSECURITY TECHNIQUES FOR DEVICE ASSISTED SERVICES, now U.S. Pat. No.8,391,834 (issued Mar. 5, 2013); application Ser. No. 12/694,451(Attorney Docket No. RALEP026), filed Jan. 27, 2010, entitled DEVICEGROUP PARTITIONS AND SETTLEMENT PLATFORM, now U.S. Pat. No. 8,548,428(issued Oct. 1, 2013); application Ser. No. 12/694,455 (Attorney DocketNo. RALEP027), filed Jan. 27, 2010, entitled DEVICE ASSISTED SERVICESINSTALL, now U.S. Pat. No. 8,402,111 (issued Mar. 19, 2013); applicationSer. No. 12/695,021 (Attorney Docket No. RALEP029), filed Jan. 27, 2010,entitled QUALITY OF SERVICE FOR DEVICE ASSISTED SERVICES, now U.S. Pat.No. 8,346,225 (issued Jan. 1, 2013); application Ser. No. 12/695,980(Attorney Docket No. RALEP030), filed Jan. 28, 2010, entitled ENHANCEDROAMING SERVICES AND CONVERGED CARRIER NETWORKS WITH DEVICE ASSISTEDSERVICES AND A PROXY, now U.S. Pat. No. 8,340,634 (issued Dec. 25,2012); application Ser. No. 13/134,005 (Attorney Docket No. RALEP049),filed May 25, 2011, entitled SYSTEM AND METHOD FOR WIRELESS NETWORKOFFLOADING, now U.S. Pat. No. 8,635,335 (issued Jan. 21, 2014);application Ser. No. 13/134,028 (Attorney Docket No. RALEP032), filedMay 25, 2011, entitled DEVICE-ASSISTED SERVICES FOR PROTECTING NETWORKCAPACITY, now U.S. Pat. No. 8,589,541 (issued Nov. 19, 2013);application Ser. No. 13/229,580 (Attorney Docket No. RALEP033), filedSep. 9, 2011, entitled WIRELESS NETWORK SERVICE INTERFACES, now U.S.Pat. No. 8,626,115 (issued Jan. 7, 2014); application Ser. No.13/237,827 (Attorney Docket No. RALEP034), filed Sep. 20, 2011, entitledADAPTING NETWORK POLICIES BASED ON DEVICE SERVICE PROCESSORCONFIGURATION, now U.S. Pat. No. 8,832,777 (issued Sep. 9, 2014);application Ser. No. 13/239,321 (Attorney Docket No. RALEP036), filedSep. 21, 2011, entitled SERVICE OFFER SET PUBLISHING TO DEVICE AGENTWITH ON-DEVICE SERVICE SELECTION, now U.S. Pat. No. 8,898,293;application Ser. No. 13/248,028 (Attorney Docket No. RALEP037), filedSep. 28, 2011, entitled ENTERPRISE ACCESS CONTROL AND ACCOUNTINGALLOCATION FOR ACCESS NETWORKS, now U.S. Pat. No. 8,924,469; applicationSer. No. 13/247,998 (Attorney Docket No. RALEP038), filed Sep. 28, 2011,entitled COMMUNICATIONS DEVICE WITH SECURE DATA PATH PROCESSING AGENTS,now U.S. Pat. No. 8,725,123 (issued May 13, 2014); application Ser. No.13/248,025 (Attorney Docket No. RALEP043), filed Sep. 28, 2011, entitledSERVICE DESIGN CENTER FOR DEVICE ASSISTED SERVICES, now U.S. Pat. No.8,924,543; application Ser. No. 13/253,013 (Attorney Docket No.RALEP035), filed Oct. 4, 2011, entitled SYSTEM AND METHOD FOR PROVIDINGUSER NOTIFICATIONS, now U.S. Pat. No. 8,745,191 (issued Jun. 3, 2014);application Ser. No. 13/309,556 (Attorney Docket No. RALEP040), filedDec. 1, 2011, entitled END USER DEVICE THAT SECURES AN ASSOCIATION OFAPPLICATION TO SERVICE POLICY WITH AN APPLICATION CERTIFICATE CHECK, nowU.S. Pat. No. 8,893,009; application Ser. No. 13/309,463 (AttorneyDocket No. RALEP041), filed Dec. 1, 2011, entitled SECURITY, FRAUDDETECTION, AND FRAUD MITIGATION IN DEVICE-ASSISTED SERVICES SYSTEMS, nowU.S. Pat. No. 8,793,758 (issued Jul. 29, 2014); and application Ser. No.13/441,821 (Attorney Docket No. RALEP047A), filed Apr. 6, 2012, entitledMANAGING SERVICE USER DISCOVERY AND SERVICE LAUNCH OBJECT PLACEMENT ON ADEVICE.

This document incorporates by reference for all purposes the followingprovisional patent applications: Provisional Application No. 61/206,354(Attorney Docket No. RALEP001+), filed Jan. 28, 2009, entitled SERVICESPOLICY COMMUNICATION SYSTEM AND METHOD; Provisional Application No.61/206,944 (Attorney Docket No. RALEP002+), filed Feb. 4, 2009, entitledSERVICES POLICY COMMUNICATION SYSTEM AND METHOD; Provisional ApplicationNo. 61/207,393 (Attorney Docket No. RALEP003+), filed Feb. 10, 2009,entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD; andProvisional Application No. 61/207,739 (Attorney Docket No. RALEP004+),entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD, filed Feb. 13,2009; Provisional Application No. 61/270,353 (Attorney Docket No.RALEP022+), filed on Jul. 6, 2009, entitled DEVICE ASSISTED CDRCREATION, AGGREGATION, MEDIATION AND BILLING; Provisional ApplicationNo. 61/275,208 (Attorney Docket No. RALEP023+), filed Aug. 25, 2009,entitled ADAPTIVE AMBIENT SERVICES; and Provisional Application No.61/237,753 (Attorney Docket No. RALEP024+), filed Aug. 28, 2009,entitled ADAPTIVE AMBIENT SERVICES; Provisional Application No.61/252,151 (Attorney Docket No. RALEP025+), filed Oct. 15, 2009,entitled SECURITY TECHNIQUES FOR DEVICE ASSISTED SERVICES; ProvisionalApplication No. 61/252,153 (Attorney Docket No. RALEP026+), filed Oct.15, 2009, entitled DEVICE GROUP PARTITIONS AND SETTLEMENT PLATFORM;Provisional Application No. 61/264,120 (Attorney Docket No. RALEP027+),filed Nov. 24, 2009, entitled DEVICE ASSISTED SERVICES INSTALL;Provisional Application No. 61/264,126 (Attorney Docket No. RALEP028+),filed Nov. 24, 2009, entitled DEVICE ASSISTED SERVICES ACTIVITY MAP;Provisional Application No. 61/348,022 (Attorney Docket No. RALEP031+),filed May 25, 2010, entitled DEVICE ASSISTED SERVICES FOR PROTECTINGNETWORK CAPACITY; Provisional Application No. 61/381,159 (AttorneyDocket No. RALEP032+), filed Sep. 9, 2010, entitled DEVICE ASSISTEDSERVICES FOR PROTECTING NETWORK CAPACITY; Provisional Application No.61/381,162 (Attorney Docket No. RALEP033+), filed Sep. 9, 2010, entitledSERVICE CONTROLLER INTERFACES AND WORKFLOWS; Provisional Application No.61/384,456 (Attorney Docket No. RALEP034+), filed Sep. 20, 2010,entitled SECURING SERVICE PROCESSOR WITH SPONSORED SIMS; ProvisionalApplication No. 61/389,547 (Attorney Docket No. RALEP035+), filed Oct.4, 2010, entitled USER NOTIFICATIONS FOR DEVICE ASSISTED SERVICES;Provisional Application No. 61/385,020 (Attorney Docket No. RALEP036+),filed Sep. 21, 2010, entitled SERVICE USAGE RECONCILIATION SYSTEMOVERVIEW; Provisional Application No. 61/387,243 (Attorney Docket No.RALEP037+), filed Sep. 28, 2010, entitled ENTERPRISE AND CONSUMERBILLING ALLOCATION FOR WIRELESS COMMUNICATION DEVICE SERVICE USAGEACTIVITIES; Provisional Application No. 61/387,247 (Attorney Docket No.RALEP038+), filed September 28, entitled SECURED DEVICE DATA RECORDS,2010; Provisional Application No. 61/407,358 (Attorney Docket No.RALEP039+), filed Oct. 27, 2010, entitled SERVICE CONTROLLER AND SERVICEPROCESSOR ARCHITECTURE; Provisional Application No. 61/418,507 (AttorneyDocket No. RALEP040+), filed Dec. 1, 2010, entitled APPLICATION SERVICEPROVIDER INTERFACE SYSTEM; Provisional Application No. 61/418,509(Attorney Docket No. RALEP041+), filed Dec. 1, 2010, entitled SERVICEUSAGE REPORTING RECONCILIATION AND FRAUD DETECTION FOR DEVICE ASSISTEDSERVICES; Provisional Application No. 61/420,727 (Attorney Docket No.RALEP042+), filed Dec. 7, 2010, entitled SECURE DEVICE DATA RECORDS;Provisional Application No. 61/422,565 (Attorney Docket No. RALEP043+),filed Dec. 13, 2010, entitled SERVICE DESIGN CENTER FOR DEVICE ASSISTEDSERVICES; Provisional Application No. 61/422,572 (Attorney Docket No.RALEP044+), filed Dec. 13, 2010, entitled SYSTEM INTERFACES ANDWORKFLOWS FOR DEVICE ASSISTED SERVICES; Provisional Application No.61/422,574 (Attorney Docket No. RALEP045+), filed Dec. 13, 2010,entitled SECURITY AND FRAUD DETECTION FOR DEVICE ASSISTED SERVICES;Provisional Application No. 61/435,564 (Attorney Docket No. RALEP046+),filed Jan. 24, 2011, entitled FRAMEWORK FOR DEVICE ASSISTED SERVICES;Provisional Application No. 61/472,606 (Attorney Docket No. RALEP047+),filed Apr. 6, 2011, entitled MANAGING SERVICE USER DISCOVERY AND SERVICELAUNCH OBJECT PLACEMENT ON A DEVICE; Provisional Application No.61/550,906 (Attorney Docket No. RALEP048+), filed Oct. 24, 2011,entitled SECURITY FOR DEVICE-ASSISTED SERVICES; Provisional ApplicationNo. 61/589,830 (Attorney Docket No. RALEP052+), filed Jan. 23, 2012,entitled METHODS AND APPARATUS TO PRESENT INFORMATION ABOUT VOICE,MESSAGING, AND DATA SERVICES ON WIRELESS MOBILE DEVICES; ProvisionalApplication No. 61/610,876 (Attorney Docket No. RALEP062+), filed Mar.14, 2012, entitled METHODS AND APPARATUS FOR APPLICATION PROMOTION ANDSPONSORSHIP; and Provisional Application No. 61/610,910 (Attorney DocketNo. RALEP063+), filed Mar. 14, 2012, entitled WIFI ACTIVATION BACKUPPROCESS.

1. A method performed by a network system, the method comprising:obtaining information to assist in identifying a portion of a userinterface of a wireless device, the wireless device communicativelycoupled to the network system over a wireless access network;determining a differentiating attribute of the identified portion of theuser interface; obtaining one or more service launch objects forplacement in the identified portion of the user interface; and sendingconfiguration information to the wireless device over the wirelessaccess network, the configuration information at least configured toassist the wireless device in placing the one or more service launchobjects in the identified portion of the user interface.